public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Zhenliang Wei <weizhenliang@huawei.com>
Cc: kbuild-all@01.org, ebiederm@xmission.com, oleg@redhat.com,
	colona@arista.com, akpm@linux-foundation.org,
	christian@brauner.io, arnd@arndb.de, tglx@linutronix.de,
	deepa.kernel@gmail.com, gregkh@linuxfoundation.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	weizhenliang@huawei.com
Subject: Re: [PATCH v3] signal: trace_signal_deliver when signal_group_exit
Date: Tue, 23 Apr 2019 07:01:09 +0800	[thread overview]
Message-ID: <201904230622.inKPwebE%lkp@intel.com> (raw)
In-Reply-To: <20190422145950.78056-1-weizhenliang@huawei.com>

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

Hi Zhenliang,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on linus/master]
[also build test ERROR on v5.1-rc6 next-20190418]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Zhenliang-Wei/signal-trace_signal_deliver-when-signal_group_exit/20190423-062107
config: i386-randconfig-x010-201916 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
        # 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 <lkp@intel.com>


All error/warnings (new ones prefixed by >>):

   In file included from arch/x86/include/uapi/asm/signal.h:94:0,
                    from arch/x86/include/asm/signal.h:36,
                    from include/uapi/linux/signal.h:5,
                    from include/linux/signal_types.h:10,
                    from include/linux/sched.h:28,
                    from include/linux/sched/mm.h:7,
                    from kernel/signal.c:16:
   kernel/signal.c: In function 'get_signal':
>> include/uapi/asm-generic/signal-defs.h:24:17: error: passing argument 3 of 'trace_signal_deliver' from incompatible pointer type [-Werror=incompatible-pointer-types]
    #define SIG_DFL ((__force __sighandler_t)0) /* default signal handling */
                    ^
>> kernel/signal.c:2444:50: note: in expansion of macro 'SIG_DFL'
      trace_signal_deliver(SIGKILL, SEND_SIG_NOINFO, SIG_DFL);
                                                     ^~~~~~~
   In file included from include/trace/syscall.h:5:0,
                    from include/linux/syscalls.h:86,
                    from kernel/signal.c:29:
   include/linux/tracepoint.h:235:21: note: expected 'struct k_sigaction *' but argument is of type 'void (*)(int)'
     static inline void trace_##name(proto)    \
                        ^
   include/linux/tracepoint.h:398:2: note: in expansion of macro '__DECLARE_TRACE'
     __DECLARE_TRACE(name, PARAMS(proto), PARAMS(args),  \
     ^~~~~~~~~~~~~~~
   include/linux/tracepoint.h:534:2: note: in expansion of macro 'DECLARE_TRACE'
     DECLARE_TRACE(name, PARAMS(proto), PARAMS(args))
     ^~~~~~~~~~~~~
>> include/trace/events/signal.h:96:1: note: in expansion of macro 'TRACE_EVENT'
    TRACE_EVENT(signal_deliver,
    ^~~~~~~~~~~
   cc1: some warnings being treated as errors

vim +/trace_signal_deliver +24 include/uapi/asm-generic/signal-defs.h

b1ecb4c3 include/asm-generic/signal.h Al Viro         2005-05-04  23  
b1ecb4c3 include/asm-generic/signal.h Al Viro         2005-05-04 @24  #define SIG_DFL	((__force __sighandler_t)0)	/* default signal handling */
b1ecb4c3 include/asm-generic/signal.h Al Viro         2005-05-04  25  #define SIG_IGN	((__force __sighandler_t)1)	/* ignore signal */
b1ecb4c3 include/asm-generic/signal.h Al Viro         2005-05-04  26  #define SIG_ERR	((__force __sighandler_t)-1)	/* error return from signal */
b1ecb4c3 include/asm-generic/signal.h Al Viro         2005-05-04  27  #endif
ad158879 include/asm-generic/signal.h David Woodhouse 2006-04-27  28  

:::::: The code at line 24 was first introduced by commit
:::::: b1ecb4c3a9e33cc8b93ac9cb046b535b72a15f68 [PATCH] asm/signal.h unification

:::::: TO: Al Viro <viro@www.linux.org.uk>
:::::: CC: Linus Torvalds <torvalds@ppc970.osdl.org>

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

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

  parent reply	other threads:[~2019-04-22 23:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-22 14:59 [PATCH v3] signal: trace_signal_deliver when signal_group_exit Zhenliang Wei
2019-04-22 15:25 ` Oleg Nesterov
2019-04-22 20:41 ` Greg KH
2019-04-22 23:01 ` kbuild test robot [this message]
2019-04-23  1:09 ` kbuild test robot
  -- strict thread matches above, loose matches on Subject: below --
2019-04-23 13:10 weizhenliang
2019-04-23 13:33 ` Christian Brauner
2019-04-23 13:35 ` Oleg Nesterov
2019-04-23 14:02 weizhenliang
2019-04-23 14:13 weizhenliang
2019-04-23 14:25 weizhenliang

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=201904230622.inKPwebE%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=christian@brauner.io \
    --cc=colona@arista.com \
    --cc=deepa.kernel@gmail.com \
    --cc=ebiederm@xmission.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg@redhat.com \
    --cc=stable@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=weizhenliang@huawei.com \
    /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