From: kernel test robot <lkp@intel.com>
To: Shervin Oloumi <enlightened@chromium.org>,
mic@digikod.net, viro@zeniv.linux.org.uk
Cc: oe-kbuild-all@lists.linux.dev, brauner@kernel.org, jack@suse.cz,
paul@paul-moore.com, jmorris@namei.org, serge@hallyn.com,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, gnoack@google.com,
shuah@kernel.org, jorgelo@chromium.org, allenwebb@chromium.org,
Shervin Oloumi <enlightened@chromium.org>
Subject: Re: [PATCH 2/2] landlock: add support for private bind mount
Date: Wed, 1 Jan 2025 05:03:14 +0800 [thread overview]
Message-ID: <202501010450.vIVxrod1-lkp@intel.com> (raw)
In-Reply-To: <20241231014632.589049-2-enlightened@chromium.org>
Hi Shervin,
kernel test robot noticed the following build errors:
[auto build test ERROR on fc033cf25e612e840e545f8d5ad2edd6ba613ed5]
url: https://github.com/intel-lab-lkp/linux/commits/Shervin-Oloumi/landlock-add-support-for-private-bind-mount/20241231-094806
base: fc033cf25e612e840e545f8d5ad2edd6ba613ed5
patch link: https://lore.kernel.org/r/20241231014632.589049-2-enlightened%40chromium.org
patch subject: [PATCH 2/2] landlock: add support for private bind mount
config: m68k-allyesconfig (https://download.01.org/0day-ci/archive/20250101/202501010450.vIVxrod1-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250101/202501010450.vIVxrod1-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/202501010450.vIVxrod1-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from include/linux/init.h:5,
from security/landlock/setup.c:9:
>> include/linux/build_bug.h:78:41: error: static assertion failed: "sizeof(typeof_member(union access_masks_all, masks)) == sizeof(typeof_member(union access_masks_all, all))"
78 | #define __static_assert(expr, msg, ...) _Static_assert(expr, msg)
| ^~~~~~~~~~~~~~
include/linux/build_bug.h:77:34: note: in expansion of macro '__static_assert'
77 | #define static_assert(expr, ...) __static_assert(expr, ##__VA_ARGS__, #expr)
| ^~~~~~~~~~~~~~~
security/landlock/ruleset.h:57:1: note: in expansion of macro 'static_assert'
57 | static_assert(sizeof(typeof_member(union access_masks_all, masks)) ==
| ^~~~~~~~~~~~~
vim +78 include/linux/build_bug.h
bc6245e5efd70c4 Ian Abbott 2017-07-10 60
6bab69c65013bed Rasmus Villemoes 2019-03-07 61 /**
6bab69c65013bed Rasmus Villemoes 2019-03-07 62 * static_assert - check integer constant expression at build time
6bab69c65013bed Rasmus Villemoes 2019-03-07 63 *
6bab69c65013bed Rasmus Villemoes 2019-03-07 64 * static_assert() is a wrapper for the C11 _Static_assert, with a
6bab69c65013bed Rasmus Villemoes 2019-03-07 65 * little macro magic to make the message optional (defaulting to the
6bab69c65013bed Rasmus Villemoes 2019-03-07 66 * stringification of the tested expression).
6bab69c65013bed Rasmus Villemoes 2019-03-07 67 *
6bab69c65013bed Rasmus Villemoes 2019-03-07 68 * Contrary to BUILD_BUG_ON(), static_assert() can be used at global
6bab69c65013bed Rasmus Villemoes 2019-03-07 69 * scope, but requires the expression to be an integer constant
6bab69c65013bed Rasmus Villemoes 2019-03-07 70 * expression (i.e., it is not enough that __builtin_constant_p() is
6bab69c65013bed Rasmus Villemoes 2019-03-07 71 * true for expr).
6bab69c65013bed Rasmus Villemoes 2019-03-07 72 *
6bab69c65013bed Rasmus Villemoes 2019-03-07 73 * Also note that BUILD_BUG_ON() fails the build if the condition is
6bab69c65013bed Rasmus Villemoes 2019-03-07 74 * true, while static_assert() fails the build if the expression is
6bab69c65013bed Rasmus Villemoes 2019-03-07 75 * false.
6bab69c65013bed Rasmus Villemoes 2019-03-07 76 */
6bab69c65013bed Rasmus Villemoes 2019-03-07 77 #define static_assert(expr, ...) __static_assert(expr, ##__VA_ARGS__, #expr)
6bab69c65013bed Rasmus Villemoes 2019-03-07 @78 #define __static_assert(expr, msg, ...) _Static_assert(expr, msg)
6bab69c65013bed Rasmus Villemoes 2019-03-07 79
07a368b3f55a79d Maxim Levitsky 2022-10-25 80
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-12-31 21:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-31 1:46 [PATCH 1/2] fs: add loopback/bind mount specific security hook Shervin Oloumi
2024-12-31 1:46 ` [PATCH 2/2] landlock: add support for private bind mount Shervin Oloumi
2024-12-31 21:03 ` kernel test robot [this message]
2024-12-31 5:28 ` [PATCH 1/2] fs: add loopback/bind mount specific security hook kernel test robot
2024-12-31 6:01 ` kernel test robot
2024-12-31 16:43 ` Casey Schaufler
2025-01-03 5:11 ` Paul Moore
2025-01-10 4:11 ` Shervin Oloumi
2025-01-03 11:10 ` Jan Kara
2025-01-10 4:14 ` Shervin Oloumi
2025-01-10 15:42 ` [PATCH v3 " Christian Brauner
2025-01-23 20:34 ` Mickaël Salaün
-- strict thread matches above, loose matches on Subject: below --
2025-01-10 2:10 Shervin Oloumi
2025-01-10 2:10 ` [PATCH v3 2/2] landlock: add support for private bind mount Shervin Oloumi
2025-01-23 20:34 ` Mickaël Salaün
2025-01-23 21:08 ` Mickaël Salaün
2025-01-23 22:02 ` Mickaël Salaün
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=202501010450.vIVxrod1-lkp@intel.com \
--to=lkp@intel.com \
--cc=allenwebb@chromium.org \
--cc=brauner@kernel.org \
--cc=enlightened@chromium.org \
--cc=gnoack@google.com \
--cc=jack@suse.cz \
--cc=jmorris@namei.org \
--cc=jorgelo@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mic@digikod.net \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.com \
--cc=shuah@kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).