archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <>
To: Peter Xu <>
Cc:, Johannes Weiner <>,
	Andrew Morton <>,
	Linux Memory Management List <>
Subject: [hnaz-linux-mm:master 89/340] include/linux/sched/signal.h:381:33: error: 'VM_FAULT_RETRY' undeclared; did you mean 'SIL_FAULT_MCEERR'?
Date: Tue, 10 Mar 2020 14:59:59 +0800	[thread overview]
Message-ID: <> (raw)

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

tree: master
head:   5d9ee416b5701096536c7a63c04dbe25012baa9e
commit: 133f884fbe299145671d583f255f71b63d9ad63f [89/340] mm: introduce fault_signal_pending()
config: i386-alldefconfig (attached as .config)
compiler: gcc-7 (Debian 7.5.0-5) 7.5.0
        git checkout 133f884fbe299145671d583f255f71b63d9ad63f
        # save the attached .config to linux build tree
        make ARCH=i386 

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <>

All errors (new ones prefixed by >>):

   In file included from include/uapi/linux/swab.h:6:0,
                    from include/linux/swab.h:5,
                    from include/uapi/linux/byteorder/little_endian.h:13,
                    from include/linux/byteorder/little_endian.h:5,
                    from arch/x86/include/uapi/asm/byteorder.h:5,
                    from include/uapi/linux/perf_event.h:20,
                    from include/linux/perf_event.h:17,
                    from arch/x86/events/core.c:15:
   include/linux/sched/signal.h: In function 'fault_signal_pending':
>> include/linux/sched/signal.h:381:33: error: 'VM_FAULT_RETRY' undeclared (first use in this function); did you mean 'SIL_FAULT_MCEERR'?
     return unlikely((fault_flags & VM_FAULT_RETRY) &&
   include/linux/compiler.h:78:42: note: in definition of macro 'unlikely'
    # define unlikely(x) __builtin_expect(!!(x), 0)
   include/linux/sched/signal.h:381:33: note: each undeclared identifier is reported only once for each function it appears in
     return unlikely((fault_flags & VM_FAULT_RETRY) &&
   include/linux/compiler.h:78:42: note: in definition of macro 'unlikely'
    # define unlikely(x) __builtin_expect(!!(x), 0)

vim +381 include/linux/sched/signal.h

   372	/*
   373	 * This should only be used in fault handlers to decide whether we
   374	 * should stop the current fault routine to handle the signals
   375	 * instead, especially with the case where we've got interrupted with
   376	 * a VM_FAULT_RETRY.
   377	 */
   378	static inline bool fault_signal_pending(unsigned int fault_flags,
   379						struct pt_regs *regs)
   380	{
 > 381		return unlikely((fault_flags & VM_FAULT_RETRY) &&
   382				fatal_signal_pending(current));
   383	}

0-DAY CI Kernel Test Service, Intel Corporation

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

                 reply	other threads:[~2020-03-10  7:01 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).