From: kernel test robot <lkp@intel.com>
To: Nguyen Ngoc Thang <ngocthang2710.1999@gmail.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev,
Nguyen Ngoc Thang <ngocthang2710.1999@gmail.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
syzbot+1075f6dc93f398c1857e@syzkaller.appspotmail.com
Subject: Re: [PATCH] Input: serio - don't sleep on serio_mutex from drvctl_store()
Date: Thu, 24 Sep 2026 12:09:46 +0800 [thread overview]
Message-ID: <202609241230.lUW53GKL-lkp@intel.com> (raw)
In-Reply-To: <20260919124604.210505-1-ngocthang2710.1999@gmail.com>
Hi Nguyen,
kernel test robot noticed the following build errors:
[auto build test ERROR on dtor-input/next]
[also build test ERROR on dtor-input/for-linus linus/master v7.3-rc4 next-20260922]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Nguyen-Ngoc-Thang/Input-serio-don-t-sleep-on-serio_mutex-from-drvctl_store/20260919-194604
base: https://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git next
patch link: https://lore.kernel.org/r/20260919124604.210505-1-ngocthang2710.1999%40gmail.com
patch subject: [PATCH] Input: serio - don't sleep on serio_mutex from drvctl_store()
config: x86_64-rhel-9.4 (https://download.01.org/0day-ci/archive/20260924/202609241230.lUW53GKL-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260924/202609241230.lUW53GKL-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202609241230.lUW53GKL-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from include/linux/jump_label.h:78,
from include/linux/dynamic_debug.h:6,
from include/linux/printk.h:620,
from include/asm-generic/bug.h:31,
from arch/x86/include/asm/bug.h:195,
from arch/x86/include/asm/alternative.h:9,
from arch/x86/include/asm/barrier.h:5,
from include/linux/list.h:11,
from include/linux/module.h:12,
from drivers/input/serio/serio.c:14:
drivers/input/serio/serio.c: In function 'drvctl_store':
>> drivers/input/serio/serio.c:361:45: error: implicit declaration of function 'restart_syscall'; did you mean 'do_no_restart_syscall'? [-Wimplicit-function-declaration]
361 | scoped_cond_guard(mutex_try, return restart_syscall(), &serio_mutex) {
| ^~~~~~~~~~~~~~~
include/linux/cleanup.h:457:25: note: in definition of macro '__scoped_cond_guard'
457 | _fail; \
| ^~~~~
drivers/input/serio/serio.c:361:9: note: in expansion of macro 'scoped_cond_guard'
361 | scoped_cond_guard(mutex_try, return restart_syscall(), &serio_mutex) {
| ^~~~~~~~~~~~~~~~~
vim +361 drivers/input/serio/serio.c
353
354 static ssize_t drvctl_store(struct device *dev, struct device_attribute *attr, const char *buf, size_t count)
355 {
356 struct serio *serio = to_serio_port(dev);
357 struct device_driver *drv;
358 int error;
359
360 /* Port removal holds serio_mutex and drains us: don't wait for it. */
> 361 scoped_cond_guard(mutex_try, return restart_syscall(), &serio_mutex) {
362 if (!strncmp(buf, "none", count)) {
363 serio_disconnect_port(serio);
364 } else if (!strncmp(buf, "reconnect", count)) {
365 serio_reconnect_subtree(serio);
366 } else if (!strncmp(buf, "rescan", count)) {
367 serio_disconnect_port(serio);
368 serio_find_driver(serio);
369 serio_remove_duplicate_events(serio, SERIO_RESCAN_PORT);
370 } else if ((drv = driver_find(buf, &serio_bus)) != NULL) {
371 serio_disconnect_port(serio);
372 error = serio_bind_driver(serio, to_serio_driver(drv));
373 serio_remove_duplicate_events(serio, SERIO_RESCAN_PORT);
374 if (error)
375 return error;
376 } else {
377 return -EINVAL;
378 }
379 }
380
381 return count;
382 }
383
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-09-24 4:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-19 12:46 [PATCH] Input: serio - don't sleep on serio_mutex from drvctl_store() Nguyen Ngoc Thang
2026-09-23 23:02 ` kernel test robot
2026-09-24 4:09 ` kernel test robot [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=202609241230.lUW53GKL-lkp@intel.com \
--to=lkp@intel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ngocthang2710.1999@gmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
--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 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.