linux-kernel - Re: Linux6.14-rc5: INFO: task hung in register_netdevice_notifier

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] [day] [month] [year] [list]

Message-ID: <20250316194201.21195-1-kuniyu@amazon.com>
Date: Sun, 16 Mar 2025 12:41:51 -0700
From: Kuniyuki Iwashima <kuniyu@...zon.com>
To: <stfomichev@...il.com>
CC: <aleksander.lobakin@...el.com>, <bigeasy@...utronix.de>,
	<davem@...emloft.net>, <edumazet@...gle.com>, <horms@...nel.org>,
	<jdamato@...tly.com>, <kuba@...nel.org>, <kuniyu@...zon.com>,
	<linux-kernel@...r.kernel.org>, <netdev@...r.kernel.org>,
	<pabeni@...hat.com>, <xnxc22xnxc22@...com>
Subject: Re: Linux6.14-rc5:  INFO: task hung in register_netdevice_notifier_net

From: Stanislav Fomichev <stfomichev@...il.com>
Date: Sun, 16 Mar 2025 09:54:27 -0700
> On 03/16, ffhgfv wrote:
> > Hello, I found a bug titled "   INFO: task hung in register_netdevice_notifier_net  " with modified syzkaller in the Linux6.14-rc5.
> > If you fix this issue, please add the following tag to the commit:  Reported-by: Jianzhou Zhao <xnxc22xnxc22@...com>,    xingwei lee <xrivendell7@...il.com>, Zhizhuo Tang <strforexctzzchange@...mail.com>
> 
> Haven't looked that deep, but it seems to involve a tunneling device,
> so I wonder whether it's gonna be fixed by:
> - https://patchwork.kernel.org/project/netdevbpf/patch/20250312190513.1252045-2-sdf@fomichev.me/
> - https://patchwork.kernel.org/project/netdevbpf/patch/20250312190513.1252045-3-sdf@fomichev.me/
> 
> Do you have a repro? Can you rerun with the above fixes and enable
> lockdep?

It seems lockdep is enabled but doesn't report any locking bug,
so I think this report is generated simply because of RTNL storm by
syzkaller.

I have 200+ task hung reports due to RTNL on my syzkaller instances.

The tunnel part is ip_tunnel_init_net() that takes RTNL too for
register_netdevice().