From: Ye Xiaolong <xiaolong.ye@intel.com>
To: Valdis.Kletnieks@vt.edu
Cc: Nicholas Krause <xerofoify@gmail.com>,
0day robot <fengguang.wu@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
lkp@01.org
Subject: Re: [lkp] [fs] 45ec18d5c7: BUG: KASAN: user-memory-access on address 00007f90291c7ec0
Date: Tue, 9 Aug 2016 11:20:12 +0800 [thread overview]
Message-ID: <20160809032012.GE8668@yexl-desktop> (raw)
In-Reply-To: <8352.1470708920@turing-police.cc.vt.edu>
On 08/08, Valdis.Kletnieks@vt.edu wrote:
>On Tue, 09 Aug 2016 09:17:58 +0800, Ye Xiaolong said:
>> On 08/08, Valdis.Kletnieks@vt.edu wrote:
>> > In other words - how did this patch get into a tree that 0day listens to?
>>
>> 0Day has a service to automatically capture every patchset sent to LKML
>
>Something's wrong then. Nick has proven to be such a maintainer time-sink
>that he's not allowed to post to LKML - or any other list on vger.kernel.org.
>
>So how did he get past that and get 0day to see it?
We'll add a blacklist for it, Thanks.
WARNING: multiple messages have this Message-ID (diff)
From: Ye Xiaolong <xiaolong.ye@intel.com>
To: lkp@lists.01.org
Subject: Re: [fs] 45ec18d5c7: BUG: KASAN: user-memory-access on address 00007f90291c7ec0
Date: Tue, 09 Aug 2016 11:20:12 +0800 [thread overview]
Message-ID: <20160809032012.GE8668@yexl-desktop> (raw)
In-Reply-To: <8352.1470708920@turing-police.cc.vt.edu>
[-- Attachment #1: Type: text/plain, Size: 565 bytes --]
On 08/08, Valdis.Kletnieks(a)vt.edu wrote:
>On Tue, 09 Aug 2016 09:17:58 +0800, Ye Xiaolong said:
>> On 08/08, Valdis.Kletnieks(a)vt.edu wrote:
>> > In other words - how did this patch get into a tree that 0day listens to?
>>
>> 0Day has a service to automatically capture every patchset sent to LKML
>
>Something's wrong then. Nick has proven to be such a maintainer time-sink
>that he's not allowed to post to LKML - or any other list on vger.kernel.org.
>
>So how did he get past that and get 0day to see it?
We'll add a blacklist for it, Thanks.
next prev parent reply other threads:[~2016-08-09 3:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-07 14:02 [lkp] [fs] 45ec18d5c7: BUG: KASAN: user-memory-access on address 00007f90291c7ec0 kernel test robot
2016-08-07 14:02 ` kernel test robot
2016-08-08 16:29 ` [lkp] " Valdis.Kletnieks
2016-08-09 1:17 ` Ye Xiaolong
2016-08-09 1:17 ` Ye Xiaolong
2016-08-09 1:27 ` [lkp] " Al Viro
2016-08-09 1:27 ` Al Viro
2016-08-09 3:18 ` [lkp] " Ye Xiaolong
2016-08-09 3:18 ` Ye Xiaolong
2016-08-09 2:15 ` [lkp] " Valdis.Kletnieks
2016-08-09 3:20 ` Ye Xiaolong [this message]
2016-08-09 3:20 ` Ye Xiaolong
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=20160809032012.GE8668@yexl-desktop \
--to=xiaolong.ye@intel.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=xerofoify@gmail.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 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.