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-github:work.coredump.socket 14/18] fs/pidfs.c:594:24: error: incomplete definition of type 'struct coredump_params'
Date: Tue, 6 May 2025 17:14:45 +0800 [thread overview]
Message-ID: <202505061732.sTCLwl1W-lkp@intel.com> (raw)
tree: https://github.com/brauner/linux.git work.coredump.socket
head: d8527ff7eedddbd9827f61df7c80d9870cdc1241
commit: 9f07dff1a3e95ae64112dc44a70939320ba18ceb [14/18] pidfs, coredump: add PIDFD_INFO_COREDUMP
config: powerpc64-randconfig-003-20250506 (https://download.01.org/0day-ci/archive/20250506/202505061732.sTCLwl1W-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/20250506/202505061732.sTCLwl1W-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/202505061732.sTCLwl1W-lkp@intel.com/
All errors (new ones prefixed by >>):
>> fs/pidfs.c:594:24: error: incomplete definition of type 'struct coredump_params'
594 | struct pid *pid = cprm->pid;
| ~~~~^
include/linux/elf.h:66:8: note: forward declaration of 'struct coredump_params'
66 | struct coredump_params;
| ^
fs/pidfs.c:607:42: error: incomplete definition of type 'struct coredump_params'
607 | coredump_mask = pidfs_coredump_mask(cprm->mm_flags);
| ~~~~^
include/linux/elf.h:66:8: note: forward declaration of 'struct coredump_params'
66 | struct coredump_params;
| ^
2 errors generated.
vim +594 fs/pidfs.c
591
592 void pidfs_coredump(const struct coredump_params *cprm)
593 {
> 594 struct pid *pid = cprm->pid;
595 struct pidfs_exit_info *exit_info;
596 struct dentry *dentry;
597 struct inode *inode;
598 __u32 coredump_mask = 0;
599
600 dentry = stashed_dentry_get(&pid->stashed);
601 if (WARN_ON_ONCE(!dentry))
602 return;
603
604 inode = d_inode(dentry);
605 exit_info = &pidfs_i(inode)->__pei;
606 /* Note how we were coredumped. */
607 coredump_mask = pidfs_coredump_mask(cprm->mm_flags);
608 /* Note that we actually did coredump. */
609 coredump_mask |= PIDFD_COREDUMPED;
610 /* If coredumping is set to skip we should never end up here. */
611 VFS_WARN_ON_ONCE(coredump_mask & PIDFD_COREDUMP_SKIP);
612 smp_store_release(&exit_info->coredump_mask, coredump_mask);
613 /* Fwiw, this cannot be the last reference. */
614 dput(dentry);
615 }
616
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-05-06 9:15 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=202505061732.sTCLwl1W-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox