From: patchwork-bot+netdevbpf@kernel.org
To: Nguyen Ngoc Thang <ngocthang2710.1999@gmail.com>
Cc: kuba@kernel.org, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
syzbot+b3fca27eb4005f0111f4@syzkaller.appspotmail.com
Subject: Re: [PATCH net] netdevsim: check the driver is bound in new_port/del_port
Date: Tue, 10 Nov 2026 02:55:20 +0000 [thread overview]
Message-ID: <179427932067.3612825.8436433275701655863.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261101135824.24484-1-ngocthang2710.1999@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sun, 1 Nov 2026 20:58:24 +0700 you wrote:
> new_port and del_port are attributes of the bus device, so they stay
> reachable after the driver is unbound. nsim_drv_remove() clears
> drvdata, yet both handlers pass it straight to priv_to_devlink() and
> devl_lock(), which faults on a small negative pointer:
>
> BUG: unable to handle page fault for address: fffffffffffffeb0
> RIP: 0010:__lock_acquire+0x41/0x2de0 kernel/locking/lockdep.c:5140
> Call Trace:
> lock_acquire+0x115/0x350
> mutex_lock_nested+0x55/0x1d0
> nsim_drv_port_add+0x5a/0x140 drivers/net/netdevsim/dev.c:1760
> new_port_store+0x1a5/0x280 drivers/net/netdevsim/bus.c:96
> kernfs_fop_write_iter+0x3a5/0x540
>
> [...]
Here is the summary with links:
- [net] netdevsim: check the driver is bound in new_port/del_port
https://git.kernel.org/netdev/net-next/c/98aaf4da98d2
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-11-10 2:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-01 13:58 Nguyen Ngoc Thang
2026-11-02 2:19 ` Hangbin Liu
2026-11-09 1:18 ` Hangbin Liu
2026-11-10 2:55 ` patchwork-bot+netdevbpf [this message]
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=179427932067.3612825.8436433275701655863.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ngocthang2710.1999@gmail.com \
--cc=pabeni@redhat.com \
--cc=syzbot+b3fca27eb4005f0111f4@syzkaller.appspotmail.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®