From: kbuild test robot <lkp@intel.com>
To: kbuild@lists.01.org
Subject: Re: [PATCH RFC] seccomp: Implement syscall isolation based on memory areas
Date: Mon, 01 Jun 2020 09:10:00 +0800 [thread overview]
Message-ID: <202006010909.GY47FTw1%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1710 bytes --]
CC: kbuild-all(a)lists.01.org
In-Reply-To: <20200530055953.817666-1-krisman@collabora.com>
References: <20200530055953.817666-1-krisman@collabora.com>
TO: Gabriel Krisman Bertazi <krisman@collabora.com>
Hi Gabriel,
[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on tip/x86/core]
[also build test WARNING on linus/master v5.7 next-20200529]
[cannot apply to asm-generic/master linux/master]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Gabriel-Krisman-Bertazi/seccomp-Implement-syscall-isolation-based-on-memory-areas/20200601-014401
base: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git 9cb1fd0efd195590b828b9b865421ad345a4a145
:::::: branch date: 7 hours ago
:::::: commit date: 7 hours ago
config: arm-randconfig-c024-20200531 (attached as .config)
compiler: arm-linux-gnueabi-gcc (GCC) 9.3.0
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
Reported-by: Julia Lawall <julia.lawall@lip6.fr>
coccinelle warnings: (new ones prefixed by >>)
>> kernel/seccomp.c:939:2-5: WARNING: Use BUG_ON instead of if condition followed by BUG.
Please make sure the condition has no side effects (see conditional BUG_ON definition in include/asm-generic/bug.h)
Please review and possibly fold the followup patch.
---
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: 39404 bytes --]
next reply other threads:[~2020-06-01 1:10 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-01 1:10 kbuild test robot [this message]
2020-06-01 1:10 ` [PATCH] seccomp: fix bugon.cocci warnings kbuild test robot
-- strict thread matches above, loose matches on Subject: below --
2020-06-01 9:23 [PATCH RFC] seccomp: Implement syscall isolation based on memory areas Billy Laws
2020-06-01 13:59 ` Andy Lutomirski
2020-06-01 17:48 ` hpa
2020-05-30 5:59 Gabriel Krisman Bertazi
2020-05-30 17:30 ` Kees Cook
2020-05-31 5:56 ` Gabriel Krisman Bertazi
2020-05-31 12:39 ` Paul Gofman
2020-05-31 16:49 ` Matthew Wilcox
2020-05-31 17:10 ` Paul Gofman
2020-05-31 17:31 ` Matthew Wilcox
2020-05-31 18:01 ` Paul Gofman
2020-06-01 17:54 ` Gabriel Krisman Bertazi
2020-06-01 17:53 ` Gabriel Krisman Bertazi
2020-05-30 22:09 ` Andy Lutomirski
2020-05-31 0:26 ` Gabriel Krisman Bertazi
2020-05-31 0:59 ` Andy Lutomirski
2020-05-31 12:56 ` Paul Gofman
2020-05-31 18:10 ` Andy Lutomirski
2020-05-31 18:36 ` Paul Gofman
2020-05-31 18:57 ` Andy Lutomirski
2020-05-31 19:37 ` Paul Gofman
2020-05-31 21:03 ` Andy Lutomirski
2020-06-01 18:06 ` Gabriel Krisman Bertazi
2020-06-01 20:08 ` Kees Cook
2020-06-01 23:18 ` Andy Lutomirski
2020-06-11 19:38 ` Gabriel Krisman Bertazi
2020-05-31 23:33 ` Brendan Shanks
2020-06-01 1:51 ` Andy Lutomirski
2020-06-25 23:14 ` Robert O'Callahan
2020-06-25 23:48 ` Gabriel Krisman Bertazi
2020-06-26 1:03 ` Robert O'Callahan
2020-06-01 3:20 ` kbuild test robot
2020-06-01 8:30 ` kbuild test robot
2020-06-05 6:06 ` Sargun Dhillon
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=202006010909.GY47FTw1%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild@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.