From: kernel test robot <lkp@intel.com>
To: Tzung-Bi Shih <tzungbi@kernel.org>, Kees Cook <kees@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, tzungbi@kernel.org
Subject: Re: [PATCH] lkdtm: Add lockdep related crash tests
Date: Sat, 15 Nov 2025 22:59:18 +0800 [thread overview]
Message-ID: <202511152240.uaKhTU6M-lkp@intel.com> (raw)
In-Reply-To: <20251114062535.1827309-1-tzungbi@kernel.org>
Hi Tzung-Bi,
kernel test robot noticed the following build warnings:
[auto build test WARNING on char-misc/char-misc-testing]
[also build test WARNING on char-misc/char-misc-next char-misc/char-misc-linus kees/for-next/pstore kees/for-next/kspp soc/for-next linus/master v6.18-rc5 next-20251114]
[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/Tzung-Bi-Shih/lkdtm-Add-lockdep-related-crash-tests/20251114-142702
base: char-misc/char-misc-testing
patch link: https://lore.kernel.org/r/20251114062535.1827309-1-tzungbi%40kernel.org
patch subject: [PATCH] lkdtm: Add lockdep related crash tests
config: parisc-defconfig (https://download.01.org/0day-ci/archive/20251115/202511152240.uaKhTU6M-lkp@intel.com/config)
compiler: hppa-linux-gcc (GCC) 15.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251115/202511152240.uaKhTU6M-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/202511152240.uaKhTU6M-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/misc/lkdtm/lockdep.c: In function 'lkdtm_LOCKDEP_CIRCULAR_LOCK':
>> drivers/misc/lkdtm/lockdep.c:21:48: warning: suggest braces around empty body in an 'else' statement [-Wempty-body]
21 | scoped_guard(spinlock, &lock_B);
| ^
drivers/misc/lkdtm/lockdep.c:23:48: warning: suggest braces around empty body in an 'else' statement [-Wempty-body]
23 | scoped_guard(spinlock, &lock_A);
| ^
drivers/misc/lkdtm/lockdep.c: In function 'lkdtm_LOCKDEP_INCONSISTENT_LOCK':
drivers/misc/lkdtm/lockdep.c:37:40: warning: suggest braces around empty body in an 'else' statement [-Wempty-body]
37 | scoped_guard(spinlock, &lock_A);
| ^
drivers/misc/lkdtm/lockdep.c:40:40: warning: suggest braces around empty body in an 'else' statement [-Wempty-body]
40 | scoped_guard(spinlock, &lock_A);
| ^
vim +/else +21 drivers/misc/lkdtm/lockdep.c
16
17 /* For "WARNING: possible circular locking dependency detected". */
18 static void lkdtm_LOCKDEP_CIRCULAR_LOCK(void)
19 {
20 scoped_guard(spinlock, &lock_A)
> 21 scoped_guard(spinlock, &lock_B);
22 scoped_guard(spinlock, &lock_B)
23 scoped_guard(spinlock, &lock_A);
24 }
25
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-11-15 15:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 6:25 [PATCH] lkdtm: Add lockdep related crash tests Tzung-Bi Shih
2025-11-15 14:59 ` 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=202511152240.uaKhTU6M-lkp@intel.com \
--to=lkp@intel.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tzungbi@kernel.org \
/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