From: kernel test robot <lkp@intel.com>
To: "Petr Mladek" <pmladek@suse.com>,
"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
"John Ogness" <john.ogness@linutronix.de>,
"Dan Carpenter" <error27@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev,
Steven Rostedt <rostedt@goodmis.org>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Kees Cook <kees@kernel.org>,
"Gustavo A . R . Silva" <gustavoars@kernel.org>,
David Gow <davidgow@google.com>, Arnd Bergmann <arnd@kernel.org>,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org,
Petr Mladek <pmladek@suse.com>
Subject: Re: [PATCH 2/3] printk: kunit: support offstack cpumask
Date: Thu, 3 Jul 2025 22:36:38 +0800 [thread overview]
Message-ID: <202507032226.1sEv2EJM-lkp@intel.com> (raw)
In-Reply-To: <20250702095157.110916-3-pmladek@suse.com>
Hi Petr,
kernel test robot noticed the following build errors:
[auto build test ERROR on linux-next/master]
[cannot apply to linus/master v6.16-rc4]
[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/Petr-Mladek/printk-ringbuffer-Explain-why-the-KUnit-test-ignores-failed-writes/20250702-175422
base: linux-next/master
patch link: https://lore.kernel.org/r/20250702095157.110916-3-pmladek%40suse.com
patch subject: [PATCH 2/3] printk: kunit: support offstack cpumask
config: riscv-randconfig-001-20250703 (https://download.01.org/0day-ci/archive/20250703/202507032226.1sEv2EJM-lkp@intel.com/config)
compiler: riscv64-linux-gcc (GCC) 13.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250703/202507032226.1sEv2EJM-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/202507032226.1sEv2EJM-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from kernel/printk/printk_ringbuffer_kunit_test.c:14:
kernel/printk/printk_ringbuffer_kunit_test.c: In function 'prbtest_cpumask_cleanup':
>> include/kunit/resource.h:409:32: error: cast specifies array type
409 | arg_type arg = (arg_type)in; \
| ^
kernel/printk/printk_ringbuffer_kunit_test.c:219:1: note: in expansion of macro 'KUNIT_DEFINE_ACTION_WRAPPER'
219 | KUNIT_DEFINE_ACTION_WRAPPER(prbtest_cpumask_cleanup, free_cpumask_var, cpumask_var_t);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
--
In file included from printk_ringbuffer_kunit_test.c:14:
printk_ringbuffer_kunit_test.c: In function 'prbtest_cpumask_cleanup':
>> include/kunit/resource.h:409:32: error: cast specifies array type
409 | arg_type arg = (arg_type)in; \
| ^
printk_ringbuffer_kunit_test.c:219:1: note: in expansion of macro 'KUNIT_DEFINE_ACTION_WRAPPER'
219 | KUNIT_DEFINE_ACTION_WRAPPER(prbtest_cpumask_cleanup, free_cpumask_var, cpumask_var_t);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +409 include/kunit/resource.h
b9dce8a1ed3efe David Gow 2023-05-25 392
56778b49c9a2cb David Gow 2023-11-28 393 /**
56778b49c9a2cb David Gow 2023-11-28 394 * KUNIT_DEFINE_ACTION_WRAPPER() - Wrap a function for use as a deferred action.
56778b49c9a2cb David Gow 2023-11-28 395 *
56778b49c9a2cb David Gow 2023-11-28 396 * @wrapper: The name of the new wrapper function define.
56778b49c9a2cb David Gow 2023-11-28 397 * @orig: The original function to wrap.
56778b49c9a2cb David Gow 2023-11-28 398 * @arg_type: The type of the argument accepted by @orig.
56778b49c9a2cb David Gow 2023-11-28 399 *
56778b49c9a2cb David Gow 2023-11-28 400 * Defines a wrapper for a function which accepts a single, pointer-sized
56778b49c9a2cb David Gow 2023-11-28 401 * argument. This wrapper can then be passed to kunit_add_action() and
56778b49c9a2cb David Gow 2023-11-28 402 * similar. This should be used in preference to casting a function
56778b49c9a2cb David Gow 2023-11-28 403 * directly to kunit_action_t, as casting function pointers will break
56778b49c9a2cb David Gow 2023-11-28 404 * control flow integrity (CFI), leading to crashes.
56778b49c9a2cb David Gow 2023-11-28 405 */
56778b49c9a2cb David Gow 2023-11-28 406 #define KUNIT_DEFINE_ACTION_WRAPPER(wrapper, orig, arg_type) \
56778b49c9a2cb David Gow 2023-11-28 407 static void wrapper(void *in) \
56778b49c9a2cb David Gow 2023-11-28 408 { \
56778b49c9a2cb David Gow 2023-11-28 @409 arg_type arg = (arg_type)in; \
56778b49c9a2cb David Gow 2023-11-28 410 orig(arg); \
56778b49c9a2cb David Gow 2023-11-28 411 }
56778b49c9a2cb David Gow 2023-11-28 412
56778b49c9a2cb David Gow 2023-11-28 413
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-07-03 14:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 9:51 [PATCH 0/3] printk: KUnit: Followup fixes for the new KUnit test Petr Mladek
2025-07-02 9:51 ` [PATCH 1/3] printk: ringbuffer: Explain why the KUnit test ignores failed writes Petr Mladek
2025-07-04 11:28 ` John Ogness
2025-07-02 9:51 ` [PATCH 2/3] printk: kunit: support offstack cpumask Petr Mladek
2025-07-02 20:28 ` Nathan Chancellor
2025-07-08 14:24 ` Petr Mladek
2025-07-08 14:48 ` Arnd Bergmann
2025-07-09 11:36 ` Petr Mladek
2025-07-09 12:53 ` Thomas Weißschuh
2025-07-10 13:51 ` Petr Mladek
2025-07-10 14:08 ` Arnd Bergmann
2025-09-02 13:55 ` Petr Mladek
2025-07-03 14:36 ` kernel test robot [this message]
2025-07-02 9:51 ` [PATCH 3/3] printk: kunit: Fix __counted_by() in struct prbtest_rbdata Petr Mladek
2025-07-04 11:41 ` John Ogness
2025-07-02 15:48 ` [PATCH 0/3] printk: KUnit: Followup fixes for the new KUnit test Thomas Weißschuh
2025-07-10 15:29 ` Petr Mladek
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=202507032226.1sEv2EJM-lkp@intel.com \
--to=lkp@intel.com \
--cc=arnd@kernel.org \
--cc=davidgow@google.com \
--cc=error27@gmail.com \
--cc=gustavoars@kernel.org \
--cc=john.ogness@linutronix.de \
--cc=kees@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=thomas.weissschuh@linutronix.de \
/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