* [PATCH RFC] netdevsim: fix deadlock in nsim_bus_dev_max_vfs_write()
@ 2026-07-01 13:15 syzbot
2026-07-31 8:35 ` Slawomir Stepien
0 siblings, 1 reply; 2+ messages in thread
From: syzbot @ 2026-07-01 13:15 UTC (permalink / raw)
To: syzkaller-upstream-moderation; +Cc: syzbot
There is an ABBA deadlock between the devlink instance lock and the debugfs
active file reference mechanism.
When a device is being removed (e.g., via nsim_drv_remove()), the driver
acquires the devlink instance lock and then calls
debugfs_remove_recursive(). This function blocks waiting for all active
file operations on the debugfs files to complete.
Concurrently, if a user writes to the "max_vfs" debugfs file, the VFS layer
acquires an active reference to the file. The write handler,
nsim_bus_dev_max_vfs_write(), then attempts to acquire the devlink instance
lock, which is already held by the removal task.
This creates a circular dependency resulting in a deadlock:
INFO: task blocked for more than 143 seconds.
Call Trace:
wait_for_completion+0x2ca/0x5e0 kernel/sched/completion.c:153
__debugfs_file_removed fs/debugfs/inode.c:751 [inline]
remove_one+0x2df/0x3b0 fs/debugfs/inode.c:758
__simple_recursive_removal+0x215/0x520 fs/libfs.c:623
debugfs_remove+0x5b/0x70 fs/debugfs/inode.c:781
nsim_dev_debugfs_exit drivers/net/netdevsim/dev.c:372 [inline]
nsim_drv_remove+0xc0/0x170 drivers/net/netdevsim/dev.c:1803
INFO: task blocked for more than 143 seconds.
Call Trace:
__mutex_lock+0x7bf/0x1550 kernel/locking/mutex.c:821
nsim_bus_dev_max_vfs_write+0x229/0x3d0 drivers/net/netdevsim/dev.c:276
full_proxy_write+0x127/0x1f0 fs/debugfs/file.c:388
vfs_write+0x296/0xba0 fs/read_write.c:685
To fix this, use devl_trylock() in nsim_bus_dev_max_vfs_write() instead of
devl_lock(). If the lock cannot be acquired, return -EBUSY. This aborts the
write operation, releases the debugfs active file reference, and allows the
pending debugfs_remove_recursive() to proceed.
Fixes: 012ec02ae441 ("netdevsim: convert driver to use unlocked devlink API during init/fini")
Assisted-by: Gemini:gemini-3.1-pro-preview best-expensive syzbot
Reported-by: syzbot+3147c5de186107ffc7a1@syzkaller.appspotmail.com
Closes: https://syzkaller.appspot.com/bug?extid=3147c5de186107ffc7a1
Link: https://syzkaller.appspot.com/ai_job?id=e3832a24-8c9f-416a-8161-a50e277bc628
To: "Andrew Lunn" <andrew+netdev@lunn.ch>
To: "David S. Miller" <davem@davemloft.net>
To: "Eric Dumazet" <edumazet@google.com>
To: "Jakub Kicinski" <kuba@kernel.org>
To: <netdev@vger.kernel.org>
To: "Paolo Abeni" <pabeni@redhat.com>
Cc: <linux-kernel@vger.kernel.org>
---
diff --git a/drivers/net/netdevsim/dev.c b/drivers/net/netdevsim/dev.c
index aed9ad5f1..421cd7327 100644
--- a/drivers/net/netdevsim/dev.c
+++ b/drivers/net/netdevsim/dev.c
@@ -273,7 +273,11 @@ static ssize_t nsim_bus_dev_max_vfs_write(struct file *file,
return -ENOMEM;
nsim_dev = file->private_data;
- devl_lock(priv_to_devlink(nsim_dev));
+ if (!devl_trylock(priv_to_devlink(nsim_dev))) {
+ ret = -EBUSY;
+ goto out;
+ }
+
/* Reject if VFs are configured */
if (nsim_dev_get_vfs(nsim_dev)) {
ret = -EBUSY;
@@ -285,6 +289,7 @@ static ssize_t nsim_bus_dev_max_vfs_write(struct file *file,
}
devl_unlock(priv_to_devlink(nsim_dev));
+out:
kfree(vfconfigs);
return ret;
}
base-commit: dc59e4fea9d83f03bad6bddf3fa2e52491777482
--
This is an AI-generated patch subject to moderation.
Reply with '#syz upstream' to Sign-off the patch as a human author
and send it to the upstream kernel mailing lists.
Reply with '#syz reject' to reject it ('#syz unreject' to undo).
See https://goo.gle/syzbot-ai-patches for information about AI-generated patches.
You can comment on the patch as usual, syzbot will try to address
the comments and send a new version of the patch if necessary.
syzbot engineers can be reached at syzkaller@googlegroups.com.
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH RFC] netdevsim: fix deadlock in nsim_bus_dev_max_vfs_write()
2026-07-01 13:15 [PATCH RFC] netdevsim: fix deadlock in nsim_bus_dev_max_vfs_write() syzbot
@ 2026-07-31 8:35 ` Slawomir Stepien
0 siblings, 0 replies; 2+ messages in thread
From: Slawomir Stepien @ 2026-07-31 8:35 UTC (permalink / raw)
To: syzbot; +Cc: syzkaller-upstream-moderation, syzbot
On lip 01, 2026 13:15, syzbot wrote:
> There is an ABBA deadlock between the devlink instance lock and the debugfs
> active file reference mechanism.
>
> When a device is being removed (e.g., via nsim_drv_remove()), the driver
> acquires the devlink instance lock and then calls
> debugfs_remove_recursive(). This function blocks waiting for all active
> file operations on the debugfs files to complete.
>
> Concurrently, if a user writes to the "max_vfs" debugfs file, the VFS layer
> acquires an active reference to the file. The write handler,
> nsim_bus_dev_max_vfs_write(), then attempts to acquire the devlink instance
> lock, which is already held by the removal task.
>
> This creates a circular dependency resulting in a deadlock:
>
> INFO: task blocked for more than 143 seconds.
> Call Trace:
> wait_for_completion+0x2ca/0x5e0 kernel/sched/completion.c:153
> __debugfs_file_removed fs/debugfs/inode.c:751 [inline]
> remove_one+0x2df/0x3b0 fs/debugfs/inode.c:758
> __simple_recursive_removal+0x215/0x520 fs/libfs.c:623
> debugfs_remove+0x5b/0x70 fs/debugfs/inode.c:781
> nsim_dev_debugfs_exit drivers/net/netdevsim/dev.c:372 [inline]
> nsim_drv_remove+0xc0/0x170 drivers/net/netdevsim/dev.c:1803
>
> INFO: task blocked for more than 143 seconds.
> Call Trace:
> __mutex_lock+0x7bf/0x1550 kernel/locking/mutex.c:821
> nsim_bus_dev_max_vfs_write+0x229/0x3d0 drivers/net/netdevsim/dev.c:276
> full_proxy_write+0x127/0x1f0 fs/debugfs/file.c:388
> vfs_write+0x296/0xba0 fs/read_write.c:685
>
> To fix this, use devl_trylock() in nsim_bus_dev_max_vfs_write() instead of
> devl_lock(). If the lock cannot be acquired, return -EBUSY. This aborts the
> write operation, releases the debugfs active file reference, and allows the
> pending debugfs_remove_recursive() to proceed.
>
> Fixes: 012ec02ae441 ("netdevsim: convert driver to use unlocked devlink API during init/fini")
I think this Fixes commit isn't correct. The devl_lock() was there since
aff3a925094633a5b77058b9a715efbb12fc2698 and there is a big change that before this change the
mutex_lock that was there, was also deadlocking. I would remove this line since it is not correct in
the 1st place.
> Assisted-by: Gemini:gemini-3.1-pro-preview best-expensive syzbot
> Reported-by: syzbot+3147c5de186107ffc7a1@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=3147c5de186107ffc7a1
> Link: https://syzkaller.appspot.com/ai_job?id=e3832a24-8c9f-416a-8161-a50e277bc628
> To: "Andrew Lunn" <andrew+netdev@lunn.ch>
> To: "David S. Miller" <davem@davemloft.net>
> To: "Eric Dumazet" <edumazet@google.com>
> To: "Jakub Kicinski" <kuba@kernel.org>
> To: <netdev@vger.kernel.org>
> To: "Paolo Abeni" <pabeni@redhat.com>
> Cc: <linux-kernel@vger.kernel.org>
>
> ---
> diff --git a/drivers/net/netdevsim/dev.c b/drivers/net/netdevsim/dev.c
> index aed9ad5f1..421cd7327 100644
> --- a/drivers/net/netdevsim/dev.c
> +++ b/drivers/net/netdevsim/dev.c
> @@ -273,7 +273,11 @@ static ssize_t nsim_bus_dev_max_vfs_write(struct file *file,
> return -ENOMEM;
>
> nsim_dev = file->private_data;
> - devl_lock(priv_to_devlink(nsim_dev));
> + if (!devl_trylock(priv_to_devlink(nsim_dev))) {
> + ret = -EBUSY;
> + goto out;
> + }
> +
> /* Reject if VFs are configured */
> if (nsim_dev_get_vfs(nsim_dev)) {
> ret = -EBUSY;
> @@ -285,6 +289,7 @@ static ssize_t nsim_bus_dev_max_vfs_write(struct file *file,
> }
> devl_unlock(priv_to_devlink(nsim_dev));
>
> +out:
> kfree(vfconfigs);
> return ret;
> }
>
>
> base-commit: dc59e4fea9d83f03bad6bddf3fa2e52491777482
--
Slawomir Stepien
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-07-31 8:36 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-07-01 13:15 [PATCH RFC] netdevsim: fix deadlock in nsim_bus_dev_max_vfs_write() syzbot
2026-07-31 8:35 ` Slawomir Stepien
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.