From: "Zhou, Yun" <yun.zhou@windriver.com>
To: "Jagielski, Jedrzej" <jedrzej.jagielski@intel.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"jirislaby@kernel.org" <jirislaby@kernel.org>,
"socketcan@hartkopp.net" <socketcan@hartkopp.net>,
sdf.kernel@gmail.com
Cc: "linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
"mkl@pengutronix.de" <mkl@pengutronix.de>,
"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"horms@kernel.org" <horms@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tty: ldisc: fix deadlock between ldisc_sem and rtnl_mutex
Date: Fri, 17 Jul 2026 11:42:28 +0800 [thread overview]
Message-ID: <70f854e7-b066-4f30-8ebf-71abdece45c2@windriver.com> (raw)
In-Reply-To: <PH0PR11MB5902C0DC3D8407F2701948C1F0C72@PH0PR11MB5902.namprd11.prod.outlook.com>
Hi Jagielski,
On 7/16/26 15:59, Jagielski, Jedrzej wrote:
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
> From: Yun Zhou <yun.zhou@windriver.com>
> Sent: Thursday, July 16, 2026 8:47 AM
>
>> syzbot reported a circular lock dependency involving tty ldisc_sem and
>> the networking rtnl_mutex. The full chain is:
>>
>> rtnl_mutex --> nft_commit_mutex --> ... --> ep->mtx --> ldisc_sem --> rtnl_mutex
>
> still unclear where the first mutex may come from
tty_set_ldisc()
tty_ldisc_lock() <- hold ldisc_sem
tty_ldisc_open()
slcan_open()
register_candev()
register_netdev()
rtnl_net_lock_killable() <- hold rtnl_mutex
>
>>
>> + tty_ldisc_unlock(tty);
>>
>> + /*
>
> this blank line is redundant i believe
>
Isn't it common practice to leave the first line of a multi-line comment
blank? Does it violate the coding style guidelines?
BR,
Yun
next prev parent reply other threads:[~2026-07-17 3:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 6:47 [PATCH] tty: ldisc: fix deadlock between ldisc_sem and rtnl_mutex Yun Zhou
2026-07-16 7:57 ` Greg KH
2026-07-17 3:03 ` Zhou, Yun
2026-07-17 10:51 ` Greg KH
2026-07-16 7:59 ` Jagielski, Jedrzej
2026-07-17 3:42 ` Zhou, Yun [this message]
2026-07-17 6:50 ` Oliver Hartkopp
2026-07-17 7:02 ` Jagielski, Jedrzej
2026-07-17 10:53 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=70f854e7-b066-4f30-8ebf-71abdece45c2@windriver.com \
--to=yun.zhou@windriver.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=horms@kernel.org \
--cc=jedrzej.jagielski@intel.com \
--cc=jirislaby@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf.kernel@gmail.com \
--cc=socketcan@hartkopp.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox