From: kernel test robot <lkp@intel.com>
To: Yuhao Huang <nekowong743@gmail.com>, linux-gpio@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, linus.walleij@linaro.org,
brgl@bgdev.pl, linux-kernel@vger.kernel.org,
Yuhao Huang <nekowong743@gmail.com>
Subject: Re: [PATCH] gpio: virtuser: fix UAF in configfs release path
Date: Sun, 25 Jan 2026 11:35:30 +0800 [thread overview]
Message-ID: <202601251126.ywFiWrat-lkp@intel.com> (raw)
In-Reply-To: <20260124162111.3945666-1-nekowong743@gmail.com>
Hi Yuhao,
kernel test robot noticed the following build warnings:
[auto build test WARNING on brgl/gpio/for-next]
[also build test WARNING on linus/master v6.19-rc6 next-20260123]
[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/Yuhao-Huang/gpio-virtuser-fix-UAF-in-configfs-release-path/20260125-002359
base: https://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git gpio/for-next
patch link: https://lore.kernel.org/r/20260124162111.3945666-1-nekowong743%40gmail.com
patch subject: [PATCH] gpio: virtuser: fix UAF in configfs release path
config: m68k-randconfig-r073-20260125 (https://download.01.org/0day-ci/archive/20260125/202601251126.ywFiWrat-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 11.5.0
smatch version: v0.5.0-8994-gd50c5a4c
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/202601251126.ywFiWrat-lkp@intel.com/
smatch warnings:
drivers/gpio/gpio-virtuser.c:1685 gpio_virtuser_device_config_group_release() warn: inconsistent indenting
vim +1685 drivers/gpio/gpio-virtuser.c
1680
1681 static void gpio_virtuser_device_config_group_release(struct config_item *item)
1682 {
1683 struct gpio_virtuser_device *dev = to_gpio_virtuser_device(item);
1684
> 1685 scoped_guard(mutex, &dev->lock) {
1686 if (gpio_virtuser_device_is_live(dev))
1687 gpio_virtuser_device_deactivate(dev);
1688 }
1689
1690 mutex_destroy(&dev->lock);
1691 ida_free(&gpio_virtuser_ida, dev->id);
1692 kfree(dev);
1693 }
1694
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-01-25 3:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-24 16:21 [PATCH] gpio: virtuser: fix UAF in configfs release path Yuhao Huang
2026-01-25 3:35 ` kernel test robot [this message]
2026-01-26 4:03 ` [PATCH v2] " Yuhao Huang
2026-01-27 9:15 ` Bartosz Golaszewski
2026-01-27 9:17 ` Bartosz Golaszewski
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=202601251126.ywFiWrat-lkp@intel.com \
--to=lkp@intel.com \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nekowong743@gmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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