All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC PATCH 2/3] vmcore: Add interface to write to old mem
Date: Wed, 09 Sep 2020 20:26:55 +0800	[thread overview]
Message-ID: <202009092021.jxS72ZBS%lkp@intel.com> (raw)
In-Reply-To: <20200909075016.104407-3-kasong@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 3913 bytes --]

Hi Kairui,

[FYI, it's a private test report for your RFC patch.]
[auto build test ERROR on linux/master]
[also build test ERROR on tip/x86/core linus/master v5.9-rc4 next-20200908]
[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]

url:    https://github.com/0day-ci/linux/commits/Kairui-Song/Add-writing-support-to-vmcore-for-reusing-oldmem/20200909-155222
base:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git bcf876870b95592b52519ed4aafcf9d95999bc9c
config: nios2-randconfig-r026-20200909 (attached as .config)
compiler: nios2-linux-gcc (GCC) 9.3.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
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=nios2 

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 net/core/dev.c:140:
   include/linux/crash_dump.h: In function 'read_from_oldmem':
>> include/linux/crash_dump.h:131:40: error: parameter name omitted
     131 | static inline ssize_t read_from_oldmem(char*, size_t, u64*, int, bool)
         |                                        ^~~~~
   include/linux/crash_dump.h:131:47: error: parameter name omitted
     131 | static inline ssize_t read_from_oldmem(char*, size_t, u64*, int, bool)
         |                                               ^~~~~~
   include/linux/crash_dump.h:131:55: error: parameter name omitted
     131 | static inline ssize_t read_from_oldmem(char*, size_t, u64*, int, bool)
         |                                                       ^~~~
   include/linux/crash_dump.h:131:61: error: parameter name omitted
     131 | static inline ssize_t read_from_oldmem(char*, size_t, u64*, int, bool)
         |                                                             ^~~
   include/linux/crash_dump.h:131:66: error: parameter name omitted
     131 | static inline ssize_t read_from_oldmem(char*, size_t, u64*, int, bool)
         |                                                                  ^~~~
   include/linux/crash_dump.h: At top level:
>> include/linux/crash_dump.h:136:1: error: expected identifier or '(' before '{' token
     136 | {
         | ^
   include/linux/crash_dump.h:135:23: warning: 'write_to_oldmem' declared 'static' but never defined [-Wunused-function]
     135 | static inline ssize_t write_to_oldmem(char*, size_t, u64*, int, bool);
         |                       ^~~~~~~~~~~~~~~

# https://github.com/0day-ci/linux/commit/6d641ec8d1a1d979916bca93ddf975a9a860c8f2
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Kairui-Song/Add-writing-support-to-vmcore-for-reusing-oldmem/20200909-155222
git checkout 6d641ec8d1a1d979916bca93ddf975a9a860c8f2
vim +131 include/linux/crash_dump.h

   122	
   123	#ifdef CONFIG_PROC_VMCORE
   124	ssize_t read_from_oldmem(char *buf, size_t count,
   125				 u64 *ppos, int userbuf,
   126				 bool encrypted);
   127	ssize_t write_to_oldmem(char *buf, size_t count,
   128				u64 *ppos, int userbuf,
   129				bool encrypted);
   130	#else
 > 131	static inline ssize_t read_from_oldmem(char*, size_t, u64*, int, bool)
   132	{
   133		return -EOPNOTSUPP;
   134	}
   135	static inline ssize_t write_to_oldmem(char*, size_t, u64*, int, bool);
 > 136	{
   137		return -EOPNOTSUPP;
   138	}
   139	#endif /* CONFIG_PROC_VMCORE */
   140	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 22524 bytes --]

  reply	other threads:[~2020-09-09 12:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-09  7:50 [RFC PATCH 0/3] Add writing support to vmcore for reusing oldmem Kairui Song
2020-09-09  7:50 ` Kairui Song
2020-09-09  7:50 ` [RFC PATCH 1/3] vmcore: simplify read_from_olemem Kairui Song
2020-09-09  7:50   ` Kairui Song
2020-09-09 10:55   ` kernel test robot
2020-09-09  7:50 ` [RFC PATCH 2/3] vmcore: Add interface to write to old mem Kairui Song
2020-09-09  7:50   ` Kairui Song
2020-09-09 12:26   ` kernel test robot [this message]
2020-09-09 12:27   ` kernel test robot
2020-09-09  7:50 ` [RFC PATCH 3/3] x86_64: implement copy_to_oldmem_page Kairui Song
2020-09-09  7:50   ` Kairui Song
2020-09-09 14:04 ` [RFC PATCH 0/3] Add writing support to vmcore for reusing oldmem Eric W. Biederman
2020-09-09 14:04   ` Eric W. Biederman
2020-09-09 16:43   ` Kairui Song
2020-09-09 16:43     ` Kairui Song
2020-09-21  7:17     ` Kairui Song
2020-09-21  7:17       ` Kairui Song

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=202009092021.jxS72ZBS%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.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 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.