linux-kernel - Re: [lkp] [fs] 45ec18d5c7: BUG: KASAN: user-memory-access on address 00007f90291c7ec0

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20160809032012.GE8668@yexl-desktop>
Date:	Tue, 9 Aug 2016 11:20:12 +0800
From:	Ye Xiaolong <xiaolong.ye@...el.com>
To:	Valdis.Kletnieks@...edu
Cc:	Nicholas Krause <xerofoify@...il.com>,
	0day robot <fengguang.wu@...el.com>,
	LKML <linux-kernel@...r.kernel.org>, lkp@...org
Subject: Re: [lkp] [fs] 45ec18d5c7: BUG: KASAN: user-memory-access on address
 00007f90291c7ec0

On 08/08, Valdis.Kletnieks@...edu wrote:
>On Tue, 09 Aug 2016 09:17:58 +0800, Ye Xiaolong said:
>> On 08/08, Valdis.Kletnieks@...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.