From: kernel test robot <lkp@intel.com>
To: Christian Brauner <brauner@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Christian Brauner <christianvanbrauner@gmail.com>
Subject: [brauner-vfs:vfs-6.15.pidfs 3/3] fs/pidfs.c:868:2: error: call to '__compiletime_assert_339' declared with 'error' attribute: BUILD_BUG_ON failed: O_DSYNC != CLONE_PIDFD
Date: Mon, 17 Mar 2025 15:36:47 +0800 [thread overview]
Message-ID: <202503171528.azXWAvUl-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git vfs-6.15.pidfs
head: b0f4119d8b2a680c8cd019f41c64e8b5444c6b83
commit: b0f4119d8b2a680c8cd019f41c64e8b5444c6b83 [3/3] pidfs: ensure that PIDFS_INFO_EXIT is available
config: mips-bcm47xx_defconfig (https://download.01.org/0day-ci/archive/20250317/202503171528.azXWAvUl-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250317/202503171528.azXWAvUl-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/202503171528.azXWAvUl-lkp@intel.com/
All errors (new ones prefixed by >>):
>> fs/pidfs.c:868:2: error: call to '__compiletime_assert_339' declared with 'error' attribute: BUILD_BUG_ON failed: O_DSYNC != CLONE_PIDFD
868 | BUILD_BUG_ON(O_DSYNC != CLONE_PIDFD);
| ^
include/linux/build_bug.h:50:2: note: expanded from macro 'BUILD_BUG_ON'
50 | BUILD_BUG_ON_MSG(condition, "BUILD_BUG_ON failed: " #condition)
| ^
include/linux/build_bug.h:39:37: note: expanded from macro 'BUILD_BUG_ON_MSG'
39 | #define BUILD_BUG_ON_MSG(cond, msg) compiletime_assert(!(cond), msg)
| ^
include/linux/compiler_types.h:542:2: note: expanded from macro 'compiletime_assert'
542 | _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__)
| ^
include/linux/compiler_types.h:530:2: note: expanded from macro '_compiletime_assert'
530 | __compiletime_assert(condition, msg, prefix, suffix)
| ^
include/linux/compiler_types.h:523:4: note: expanded from macro '__compiletime_assert'
523 | prefix ## suffix(); \
| ^
<scratch space>:107:1: note: expanded from here
107 | __compiletime_assert_339
| ^
1 error generated.
vim +868 fs/pidfs.c
862
863 struct file *pidfd_file;
864 struct path path __free(path_put) = {};
865 unsigned int pidfd_flags = (flags & ~CLONE_PIDFD);
866 int ret;
867
> 868 BUILD_BUG_ON(O_DSYNC != CLONE_PIDFD);
869
870 ret = path_from_stashed(&pid->stashed, pidfs_mnt, get_pid(pid), &path);
871 if (ret < 0)
872 return ERR_PTR(ret);
873
874 if (!pidfs_pid_valid(pid, &path, flags))
875 return ERR_PTR(-ESRCH);
876
877 pidfd_file = dentry_open(&path, pidfd_flags, current_cred());
878 /* Raise PIDFD_THREAD explicitly as do_dentry_open() strips it. */
879 if (!IS_ERR(pidfd_file))
880 pidfd_file->f_flags |= (pidfd_flags & PIDFD_THREAD);
881
882 return pidfd_file;
883 }
884
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-03-17 7:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202503171528.azXWAvUl-lkp@intel.com \
--to=lkp@intel.com \
--cc=brauner@kernel.org \
--cc=christianvanbrauner@gmail.com \
--cc=llvm@lists.linux.dev \
--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 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.