From: Nguyen Ngoc Thang <ngocthang2710.1999@gmail.com>
To: dmitry.torokhov@gmail.com
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
sashiko-bot@kernel.org,
syzbot+1075f6dc93f398c1857e@syzkaller.appspotmail.com,
lkp@intel.com, Nguyen Ngoc Thang <ngocthang2710.1999@gmail.com>
Subject: [PATCH v3] Input: serio - don't sleep on serio_mutex from drvctl_store()
Date: Thu, 24 Sep 2026 11:32:02 +0700 [thread overview]
Message-ID: <20260924043202.719245-1-ngocthang2710.1999@gmail.com> (raw)
Writing to the drvctl attribute takes serio_mutex while holding the
attribute's kernfs active reference. serio_unregister_port() does the
opposite: it holds serio_mutex and device_del() then waits for active
references to drain in kernfs_drain(). If a drvctl write is in flight
when the port is unregistered, the writer waits for serio_mutex and the
unregistering task waits for the writer, and neither makes progress.
Interruptibility of the lock does not help, as nothing signals the writer.
lockdep reports it as:
WARNING: possible circular locking dependency detected
repro/4908 is trying to acquire lock:
(kn->active){++++}-{0:0}, at: __kernfs_remove+0x34c/0xb90
but task is already holding lock:
(serio_mutex){+.+.}-{4:4}, at: serio_unregister_port+0x1b/0x40
drvctl_store
sysfs_kf_write
...
kernfs_drain
device_del
serio_destroy_port
serio_unregister_port
userio_char_release
Use mutex_trylock() and restart the syscall when the mutex is busy, so
the active reference is dropped before waiting. Once the port is being
removed the retried write fails with -ENODEV.
Reported-by: syzbot+1075f6dc93f398c1857e@syzkaller.appspotmail.com
Closes: https://syzkaller.appspot.com/bug?extid=1075f6dc93f398c1857e
Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
Signed-off-by: Nguyen Ngoc Thang <ngocthang2710.1999@gmail.com>
---
drivers/input/serio/serio.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/input/serio/serio.c b/drivers/input/serio/serio.c
index 54dd26249b02..ebee89adc8a6 100644
--- a/drivers/input/serio/serio.c
+++ b/drivers/input/serio/serio.c
@@ -15,6 +15,7 @@
#include <linux/serio.h>
#include <linux/errno.h>
#include <linux/sched.h>
+#include <linux/sched/signal.h>
#include <linux/slab.h>
#include <linux/workqueue.h>
#include <linux/mutex.h>
@@ -357,7 +358,8 @@ static ssize_t drvctl_store(struct device *dev, struct device_attribute *attr, c
struct device_driver *drv;
int error;
- scoped_cond_guard(mutex_intr, return -EINTR, &serio_mutex) {
+ /* Removal holds serio_mutex and waits for us: retry, don't sleep. */
+ scoped_cond_guard(mutex_try, return restart_syscall(), &serio_mutex) {
if (!strncmp(buf, "none", count)) {
serio_disconnect_port(serio);
} else if (!strncmp(buf, "reconnect", count)) {
base-commit: daae2ab46e0cb612f50ca1d86cf50e5962461ae5
--
2.43.0
reply other threads:[~2026-09-24 4:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260924043202.719245-1-ngocthang2710.1999@gmail.com \
--to=ngocthang2710.1999@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=sashiko-bot@kernel.org \
--cc=syzbot+1075f6dc93f398c1857e@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