From: kernel test robot <lkp@intel.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [ebiederm-user-namespace:coredump-vma-snapshot-fix 1/5] fs/binfmt_flat.c:121:50: error: invalid use of undefined type 'struct coredump_params'
Date: Wed, 9 Mar 2022 11:56:14 +0800 [thread overview]
Message-ID: <202203091120.1aKGFQ4H-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git coredump-vma-snapshot-fix
head: 390031c942116d4733310f0684beb8db19885fe6
commit: a99a3e2efaf1f4454eb5c9176f47e66de075b134 [1/5] coredump: Move definition of struct coredump_params into coredump.h
config: riscv-randconfig-r042-20220308 (https://download.01.org/0day-ci/archive/20220309/202203091120.1aKGFQ4H-lkp@intel.com/config)
compiler: riscv32-linux-gcc (GCC) 11.2.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git/commit/?id=a99a3e2efaf1f4454eb5c9176f47e66de075b134
git remote add ebiederm-user-namespace https://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git
git fetch --no-tags ebiederm-user-namespace coredump-vma-snapshot-fix
git checkout a99a3e2efaf1f4454eb5c9176f47e66de075b134
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=riscv SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
In file included from include/linux/kernel.h:29,
from fs/binfmt_flat.c:21:
fs/binfmt_flat.c: In function 'flat_core_dump':
>> fs/binfmt_flat.c:121:50: error: invalid use of undefined type 'struct coredump_params'
121 | current->comm, current->pid, cprm->siginfo->si_signo);
| ^~
include/linux/printk.h:418:33: note: in definition of macro 'printk_index_wrap'
418 | _p_func(_fmt, ##__VA_ARGS__); \
| ^~~~~~~~~~~
include/linux/printk.h:499:9: note: in expansion of macro 'printk'
499 | printk(KERN_WARNING pr_fmt(fmt), ##__VA_ARGS__)
| ^~~~~~
fs/binfmt_flat.c:120:9: note: in expansion of macro 'pr_warn'
120 | pr_warn("Process %s:%d received signr %d and should have core dumped\n",
| ^~~~~~~
At top level:
fs/binfmt_flat.c:118:12: warning: 'flat_core_dump' defined but not used [-Wunused-function]
118 | static int flat_core_dump(struct coredump_params *cprm)
| ^~~~~~~~~~~~~~
vim +121 fs/binfmt_flat.c
^1da177e4c3f415 Linus Torvalds 2005-04-16 111
^1da177e4c3f415 Linus Torvalds 2005-04-16 112 /****************************************************************************/
^1da177e4c3f415 Linus Torvalds 2005-04-16 113 /*
^1da177e4c3f415 Linus Torvalds 2005-04-16 114 * Routine writes a core dump image in the current directory.
^1da177e4c3f415 Linus Torvalds 2005-04-16 115 * Currently only a stub-function.
^1da177e4c3f415 Linus Torvalds 2005-04-16 116 */
^1da177e4c3f415 Linus Torvalds 2005-04-16 117
f6151dfea21496d Masami Hiramatsu 2009-12-17 118 static int flat_core_dump(struct coredump_params *cprm)
^1da177e4c3f415 Linus Torvalds 2005-04-16 119 {
4adbb6ac4b807e2 Nicolas Pitre 2016-07-24 120 pr_warn("Process %s:%d received signr %d and should have core dumped\n",
13c3f50c914e6a5 Nicolas Pitre 2016-07-24 @121 current->comm, current->pid, cprm->siginfo->si_signo);
13c3f50c914e6a5 Nicolas Pitre 2016-07-24 122 return 1;
^1da177e4c3f415 Linus Torvalds 2005-04-16 123 }
^1da177e4c3f415 Linus Torvalds 2005-04-16 124
:::::: The code at line 121 was first introduced by commit
:::::: 13c3f50c914e6a51d11e1aba4a85c2223e197e13 binfmt_flat: assorted cleanups
:::::: TO: Nicolas Pitre <nicolas.pitre@linaro.org>
:::::: CC: Greg Ungerer <gerg@linux-m68k.org>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2022-03-09 3:56 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=202203091120.1aKGFQ4H-lkp@intel.com \
--to=lkp@intel.com \
--cc=ebiederm@xmission.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.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