All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: arch/x86/lib/copy_mc.c:30:1: warning: no previous prototype for 'copy_mc_fragile_handle_tail'
Date: Wed, 28 Apr 2021 16:32:30 +0800	[thread overview]
Message-ID: <202104281624.kLmwCly0-lkp@intel.com> (raw)

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

Hi Dan,

FYI, the error/warning still remains.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   acd3d28594536e9096c1ea76c5867d8a68babef6
commit: ec6347bb43395cb92126788a1a5b25302543f815 x86, powerpc: Rename memcpy_mcsafe() to copy_mc_to_{user, kernel}()
date:   7 months ago
config: x86_64-randconfig-r016-20210428 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
        # https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ec6347bb43395cb92126788a1a5b25302543f815
        git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
        git fetch --no-tags linus master
        git checkout ec6347bb43395cb92126788a1a5b25302543f815
        # save the attached .config to linux build tree
        make W=1 W=1 ARCH=x86_64 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All warnings (new ones prefixed by >>):

>> arch/x86/lib/copy_mc.c:30:1: warning: no previous prototype for 'copy_mc_fragile_handle_tail' [-Wmissing-prototypes]
      30 | copy_mc_fragile_handle_tail(char *to, char *from, unsigned len)
         | ^~~~~~~~~~~~~~~~~~~~~~~~~~~


vim +/copy_mc_fragile_handle_tail +30 arch/x86/lib/copy_mc.c

    24	
    25	/*
    26	 * Similar to copy_user_handle_tail, probe for the write fault point, or
    27	 * source exception point.
    28	 */
    29	__visible notrace unsigned long
  > 30	copy_mc_fragile_handle_tail(char *to, char *from, unsigned len)
    31	{
    32		for (; len; --len, to++, from++)
    33			if (copy_mc_fragile(to, from, 1))
    34				break;
    35		return len;
    36	}
    37	#else
    38	/*
    39	 * No point in doing careful copying, or consulting a static key when
    40	 * there is no #MC handler in the CONFIG_X86_MCE=n case.
    41	 */
    42	void enable_copy_mc_fragile(void)
    43	{
    44	}
    45	#define copy_mc_fragile_enabled (0)
    46	#endif
    47	

---
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: 37140 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
	Borislav Petkov <bp@suse.de>, Tony Luck <tony.luck@intel.com>
Subject: arch/x86/lib/copy_mc.c:30:1: warning: no previous prototype for 'copy_mc_fragile_handle_tail'
Date: Wed, 28 Apr 2021 16:32:30 +0800	[thread overview]
Message-ID: <202104281624.kLmwCly0-lkp@intel.com> (raw)

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

Hi Dan,

FYI, the error/warning still remains.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   acd3d28594536e9096c1ea76c5867d8a68babef6
commit: ec6347bb43395cb92126788a1a5b25302543f815 x86, powerpc: Rename memcpy_mcsafe() to copy_mc_to_{user, kernel}()
date:   7 months ago
config: x86_64-randconfig-r016-20210428 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
        # https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ec6347bb43395cb92126788a1a5b25302543f815
        git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
        git fetch --no-tags linus master
        git checkout ec6347bb43395cb92126788a1a5b25302543f815
        # save the attached .config to linux build tree
        make W=1 W=1 ARCH=x86_64 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All warnings (new ones prefixed by >>):

>> arch/x86/lib/copy_mc.c:30:1: warning: no previous prototype for 'copy_mc_fragile_handle_tail' [-Wmissing-prototypes]
      30 | copy_mc_fragile_handle_tail(char *to, char *from, unsigned len)
         | ^~~~~~~~~~~~~~~~~~~~~~~~~~~


vim +/copy_mc_fragile_handle_tail +30 arch/x86/lib/copy_mc.c

    24	
    25	/*
    26	 * Similar to copy_user_handle_tail, probe for the write fault point, or
    27	 * source exception point.
    28	 */
    29	__visible notrace unsigned long
  > 30	copy_mc_fragile_handle_tail(char *to, char *from, unsigned len)
    31	{
    32		for (; len; --len, to++, from++)
    33			if (copy_mc_fragile(to, from, 1))
    34				break;
    35		return len;
    36	}
    37	#else
    38	/*
    39	 * No point in doing careful copying, or consulting a static key when
    40	 * there is no #MC handler in the CONFIG_X86_MCE=n case.
    41	 */
    42	void enable_copy_mc_fragile(void)
    43	{
    44	}
    45	#define copy_mc_fragile_enabled (0)
    46	#endif
    47	

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

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

             reply	other threads:[~2021-04-28  8:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-28  8:32 kernel test robot [this message]
2021-04-28  8:32 ` arch/x86/lib/copy_mc.c:30:1: warning: no previous prototype for 'copy_mc_fragile_handle_tail' kernel test robot
  -- strict thread matches above, loose matches on Subject: below --
2021-06-09 22:43 kernel test robot
2021-06-09 22:43 ` kernel test robot
2021-06-09 23:43 ` Dan Williams
2021-06-09 23:43   ` Dan Williams
2021-06-09 23:55   ` Luck, Tony
2021-06-09 23:55     ` Luck, Tony
2021-06-10  0:13     ` Dan Williams
2021-06-10  0:13       ` Dan Williams
2021-03-30 18:10 kernel test robot
2021-03-30 18:10 ` kernel test robot

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=202104281624.kLmwCly0-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.