From: Stanislav Fomichev <stfomichev@gmail.com>
To: ffhgfv <xnxc22xnxc22@qq.com>
Cc: davem <davem@davemloft.net>, edumazet <edumazet@google.com>,
kuba <kuba@kernel.org>, pabeni <pabeni@redhat.com>,
horms <horms@kernel.org>, kuniyu <kuniyu@amazon.com>,
bigeasy <bigeasy@linutronix.de>, jdamato <jdamato@fastly.com>,
"aleksander.lobakin" <aleksander.lobakin@intel.com>,
netdev <netdev@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Linux6.14-rc5: INFO: task hung in register_netdevice_notifier_net
Date: Sun, 16 Mar 2025 09:54:27 -0700 [thread overview]
Message-ID: <Z9cCQ1huViMjZkvS@mini-arch> (raw)
In-Reply-To: <tencent_A3FB41E607B2126D163C5D4C87DC196E0707@qq.com>
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@qq.com>, xingwei lee <xrivendell7@gmail.com>, Zhizhuo Tang <strforexctzzchange@foxmail.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?
next prev parent reply other threads:[~2025-03-16 16:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-16 11:01 Linux6.14-rc5: INFO: task hung in register_netdevice_notifier_net ffhgfv
2025-03-16 16:54 ` Stanislav Fomichev [this message]
2025-03-16 19:41 ` Kuniyuki Iwashima
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=Z9cCQ1huViMjZkvS@mini-arch \
--to=stfomichev@gmail.com \
--cc=aleksander.lobakin@intel.com \
--cc=bigeasy@linutronix.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jdamato@fastly.com \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=xnxc22xnxc22@qq.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.