From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com, Dan Carpenter <error27@gmail.com>
Subject: Re: [PATCH 20/22] gpio: protect the pointer to gpio_chip in gpio_device with SRCU
Date: Thu, 1 Feb 2024 06:49:17 +0800 [thread overview]
Message-ID: <202402010641.idtEaO24-lkp@intel.com> (raw)
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20240130124828.14678-21-brgl@bgdev.pl>
References: <20240130124828.14678-21-brgl@bgdev.pl>
TO: Bartosz Golaszewski <brgl@bgdev.pl>
TO: Linus Walleij <linus.walleij@linaro.org>
TO: Kent Gibson <warthog618@gmail.com>
TO: Alex Elder <elder@linaro.org>
TO: Geert Uytterhoeven <geert+renesas@glider.be>
TO: "Paul E . McKenney" <paulmck@kernel.org>
TO: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
TO: Wolfram Sang <wsa-dev@sang-engineering.com>
CC: linux-gpio@vger.kernel.org
CC: linux-kernel@vger.kernel.org
CC: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Hi Bartosz,
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.8-rc2 next-20240131]
[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/Bartosz-Golaszewski/gpio-protect-the-list-of-GPIO-devices-with-SRCU/20240130-205537
base: https://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git gpio/for-next
patch link: https://lore.kernel.org/r/20240130124828.14678-21-brgl%40bgdev.pl
patch subject: [PATCH 20/22] gpio: protect the pointer to gpio_chip in gpio_device with SRCU
:::::: branch date: 34 hours ago
:::::: commit date: 34 hours ago
config: i386-randconfig-141-20240131 (https://download.01.org/0day-ci/archive/20240201/202402010641.idtEaO24-lkp@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
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>
| Reported-by: Dan Carpenter <error27@gmail.com>
| Closes: https://lore.kernel.org/r/202402010641.idtEaO24-lkp@intel.com/
New smatch warnings:
drivers/gpio/gpiolib.c:4776 gpiolib_dbg_show() error: we previously assumed 'gc' could be null (see line 4773)
Old smatch warnings:
drivers/gpio/gpiolib.c:4222 gpiod_find_and_request() error: uninitialized symbol 'ret'.
drivers/gpio/gpiolib.c:4236 gpiod_find_and_request() error: uninitialized symbol 'desc'.
drivers/gpio/gpiolib.c:4239 gpiod_find_and_request() error: uninitialized symbol 'desc'.
vim +/gc +4776 drivers/gpio/gpiolib.c
d2876d08d86f22 David Brownell 2008-02-04 4761
fdeb8e1547cb9d Linus Walleij 2016-02-10 4762 static void gpiolib_dbg_show(struct seq_file *s, struct gpio_device *gdev)
d2876d08d86f22 David Brownell 2008-02-04 4763 {
0338f6a6fb659f Bartosz Golaszewski 2023-12-21 4764 bool active_low, is_irq, is_out;
0338f6a6fb659f Bartosz Golaszewski 2023-12-21 4765 unsigned int gpio = gdev->base;
3de69ae1c407da Andy Shevchenko 2022-04-08 4766 struct gpio_desc *desc;
2796d5332f8ac8 Bartosz Golaszewski 2024-01-30 4767 struct gpio_chip *gc;
3de69ae1c407da Andy Shevchenko 2022-04-08 4768 int value;
d2876d08d86f22 David Brownell 2008-02-04 4769
2796d5332f8ac8 Bartosz Golaszewski 2024-01-30 4770 guard(srcu)(&gdev->srcu);
2796d5332f8ac8 Bartosz Golaszewski 2024-01-30 4771
2796d5332f8ac8 Bartosz Golaszewski 2024-01-30 4772 gc = rcu_dereference(gdev->chip);
2796d5332f8ac8 Bartosz Golaszewski 2024-01-30 @4773 if (!gc)
2796d5332f8ac8 Bartosz Golaszewski 2024-01-30 4774 seq_puts(s, "Underlying GPIO chip is gone\n");
2796d5332f8ac8 Bartosz Golaszewski 2024-01-30 4775
3de69ae1c407da Andy Shevchenko 2022-04-08 @4776 for_each_gpio_desc(gc, desc) {
bedc56b1695b27 Bartosz Golaszewski 2024-01-30 4777 guard(srcu)(&desc->srcu);
3de69ae1c407da Andy Shevchenko 2022-04-08 4778 if (test_bit(FLAG_REQUESTED, &desc->flags)) {
3de69ae1c407da Andy Shevchenko 2022-04-08 4779 gpiod_get_direction(desc);
3de69ae1c407da Andy Shevchenko 2022-04-08 4780 is_out = test_bit(FLAG_IS_OUT, &desc->flags);
234c52097ce416 Andy Shevchenko 2022-04-08 4781 value = gpio_chip_get_value(gc, desc);
3de69ae1c407da Andy Shevchenko 2022-04-08 4782 is_irq = test_bit(FLAG_USED_AS_IRQ, &desc->flags);
3de69ae1c407da Andy Shevchenko 2022-04-08 4783 active_low = test_bit(FLAG_ACTIVE_LOW, &desc->flags);
3de69ae1c407da Andy Shevchenko 2022-04-08 4784 seq_printf(s, " gpio-%-3d (%-20.20s|%-20.20s) %s %s %s%s\n",
32648f473c7f46 Bartosz Golaszewski 2024-01-30 4785 gpio, desc->name ?: "", gpiod_get_label(desc),
d2876d08d86f22 David Brownell 2008-02-04 4786 is_out ? "out" : "in ",
3de69ae1c407da Andy Shevchenko 2022-04-08 4787 value >= 0 ? (value ? "hi" : "lo") : "? ",
90fd227029a25b Linus Walleij 2018-10-01 4788 is_irq ? "IRQ " : "",
90fd227029a25b Linus Walleij 2018-10-01 4789 active_low ? "ACTIVE LOW" : "");
3de69ae1c407da Andy Shevchenko 2022-04-08 4790 } else if (desc->name) {
3de69ae1c407da Andy Shevchenko 2022-04-08 4791 seq_printf(s, " gpio-%-3d (%-20.20s)\n", gpio, desc->name);
3de69ae1c407da Andy Shevchenko 2022-04-08 4792 }
3de69ae1c407da Andy Shevchenko 2022-04-08 4793
3de69ae1c407da Andy Shevchenko 2022-04-08 4794 gpio++;
d2876d08d86f22 David Brownell 2008-02-04 4795 }
d2876d08d86f22 David Brownell 2008-02-04 4796 }
d2876d08d86f22 David Brownell 2008-02-04 4797
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-01-31 22:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 22:49 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-30 12:48 [PATCH 00/22] gpio: rework locking and object life-time control Bartosz Golaszewski
2024-01-30 12:48 ` [PATCH 20/22] gpio: protect the pointer to gpio_chip in gpio_device with SRCU Bartosz Golaszewski
2024-01-31 0:41 ` kernel test robot
2024-01-31 8:15 ` Bartosz Golaszewski
2024-01-31 2:20 ` kernel test robot
2024-01-31 9:02 ` Bartosz Golaszewski
2024-01-31 9:24 ` Paul E. McKenney
2024-01-31 9:28 ` Bartosz Golaszewski
2024-01-31 9:41 ` Bartosz Golaszewski
2024-01-31 9:42 ` Paul E. McKenney
2024-01-31 10:17 ` brgl
2024-01-31 11:00 ` Paul E. McKenney
2024-01-31 12:23 ` Bartosz Golaszewski
2024-01-31 20:23 ` Linus Walleij
2024-02-01 5:03 ` Dan Carpenter
2024-02-01 7:57 ` 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=202402010641.idtEaO24-lkp@intel.com \
--to=lkp@intel.com \
--cc=error27@gmail.com \
--cc=oe-kbuild@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 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.