From: Johannes Berg <johannes@sipsolutions.net>
To: Sam Sun <samsun1006219@gmail.com>,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, Simon Horman <horms@kernel.org>,
pabeni@redhat.com, kuba@kernel.org,
Eric Dumazet <edumazet@google.com>,
davem@davemloft.net, krzk@kernel.org
Subject: Re: [Bug] Deadlock between rfkill_fop_write() and nfc_unregister_device()
Date: Tue, 17 Dec 2024 12:33:22 +0100 [thread overview]
Message-ID: <de5d98be99086a7182ba2bd0676b261349a145c4.camel@sipsolutions.net> (raw)
In-Reply-To: <b27dc4d0c3456c6796437b26b887b931d9871977.camel@sipsolutions.net>
On Tue, 2024-12-17 at 11:46 +0100, Johannes Berg wrote:
> On Tue, 2024-12-17 at 17:33 +0800, Sam Sun wrote:
> > Dear developers and maintainers,
> >
> > We originally encountered a task hung while using our modified
> > syzkaller. It was tested against the latest upstream kernel. We
> > analyzed the root cause and pinpoint the kernel crash log to the
> > following two tasks.
> >
>
> This issue has been known a very long time and should be fixed in NFC,
> but I guess nobody is around to do it.
>
> https://syzkaller.appspot.com/bug?extid=bb540a4bbfb4ae3b425d
>
I think this one is also the same:
https://syzkaller.appspot.com/bug?extid=9ef743bba3a17c756174
and that's much older still.
johannes
next prev parent reply other threads:[~2024-12-17 11:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 9:33 Sam Sun
2024-12-17 10:46 ` Johannes Berg
2024-12-17 11:33 ` Johannes Berg [this message]
2024-12-17 12:01 ` Sam Sun
2024-12-17 12:09 ` Johannes Berg
2024-12-17 12:38 ` Krzysztof Kozlowski
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=de5d98be99086a7182ba2bd0676b261349a145c4.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=krzk@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=samsun1006219@gmail.com \
/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
all inboxes | Powered by JetHome®