linux-kernel - Re: [Bug] Deadlock between rfkill_fop_write() and nfc_unregister

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <70f796f623a67b283c4fe3a1b56e59647a39ce6c.camel@sipsolutions.net>
Date: Tue, 17 Dec 2024 13:09:42 +0100
From: Johannes Berg <johannes@...solutions.net>
To: Sam Sun <samsun1006219@...il.com>
Cc: linux-kernel@...r.kernel.org, linux-wireless@...r.kernel.org, 
	netdev@...r.kernel.org, Simon Horman <horms@...nel.org>, pabeni@...hat.com,
 	kuba@...nel.org, Eric Dumazet <edumazet@...gle.com>, davem@...emloft.net, 
	krzk@...nel.org
Subject: Re: [Bug] Deadlock between rfkill_fop_write() and
 nfc_unregister_device()

On Tue, 2024-12-17 at 20:01 +0800, Sam Sun wrote:
> On Tue, Dec 17, 2024 at 7:33 PM Johannes Berg <johannes@...solutions.net> wrote:
> > 
> > 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.
> > 
> 
> Thanks for your quick reply! I am sorry that I didn't double-check the
> call stack of historical bugs reported by Syzbot. I will be careful
> next time.
> 

No worries. Maybe someone who feels responsible for NFC will wake up ;-)

johannes