From: kbuild test robot <lkp@intel.com>
To: Jann Horn <jannh@google.com>
Cc: kbuild-all@01.org, John Johansen <john.johansen@canonical.com>,
apparmor@lists.ubuntu.com, jannh@google.com,
linux-kernel@vger.kernel.org,
Cyrill Gorcunov <gorcunov@gmail.com>,
kernel test robot <rong.a.chen@intel.com>
Subject: Re: [PATCH] apparmor: don't try to replace stale label in ptraceme check
Date: Sun, 30 Sep 2018 12:34:15 +0800 [thread overview]
Message-ID: <201809301210.HqBb3Nw1%fengguang.wu@intel.com> (raw)
In-Reply-To: <20180929014926.227002-1-jannh@google.com>
[-- Attachment #1: Type: text/plain, Size: 1918 bytes --]
Hi Jann,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on security/next]
[also build test WARNING on v4.19-rc5 next-20180928]
[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/Jann-Horn/apparmor-don-t-try-to-replace-stale-label-in-ptraceme-check/20180929-101346
base: https://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git next
config: x86_64-allmodconfig (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=x86_64
All warnings (new ones prefixed by >>):
drivers/tty/serial/8250/8250_port.c:332:14: warning: symbol 'au_serial_in' was not declared. Should it be static?
drivers/tty/serial/8250/8250_port.c:342:6: warning: symbol 'au_serial_out' was not declared. Should it be static?
>> include/linux/spinlock.h:354:9: warning: context imbalance in 'serial8250_console_write' - unexpected unlock
vim +/serial8250_console_write +354 include/linux/spinlock.h
c2f21ce2 Thomas Gleixner 2009-12-02 351
3490565b Denys Vlasenko 2015-07-13 352 static __always_inline void spin_unlock_irqrestore(spinlock_t *lock, unsigned long flags)
c2f21ce2 Thomas Gleixner 2009-12-02 353 {
c2f21ce2 Thomas Gleixner 2009-12-02 @354 raw_spin_unlock_irqrestore(&lock->rlock, flags);
c2f21ce2 Thomas Gleixner 2009-12-02 355 }
c2f21ce2 Thomas Gleixner 2009-12-02 356
:::::: The code at line 354 was first introduced by commit
:::::: c2f21ce2e31286a0a32f8da0a7856e9ca1122ef3 locking: Implement new raw_spinlock
:::::: TO: Thomas Gleixner <tglx@linutronix.de>
:::::: CC: Thomas Gleixner <tglx@linutronix.de>
---
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: 60781 bytes --]
prev parent reply other threads:[~2018-09-30 4:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-29 1:49 Jann Horn
2018-09-29 4:38 ` John Johansen
2018-09-29 23:23 ` kbuild test robot
2018-09-29 23:38 ` Jann Horn
2018-09-30 4:34 ` kbuild test robot [this message]
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=201809301210.HqBb3Nw1%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=apparmor@lists.ubuntu.com \
--cc=gorcunov@gmail.com \
--cc=jannh@google.com \
--cc=john.johansen@canonical.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rong.a.chen@intel.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
all inboxes | Powered by JetHome®