linux-kernel - Re: [i2c: dev] d6760b14d4: BUG: KASAN: slab-out-of-bounds in of_device

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] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 28 May 2016 15:24:33 +0800
From:	Fengguang Wu <fengguang.wu@...el.com>
To:	Wolfram Sang <wsa@...-dreams.de>
Cc:	Erico Nunes <erico.nunes@...acom.ind.br>, LKP <lkp@...org>,
	linux-kernel@...r.kernel.org, linux-i2c@...r.kernel.org,
	Ye Xiaolong <xiaolong.ye@...el.com>
Subject: Re: [i2c: dev] d6760b14d4:  BUG: KASAN: slab-out-of-bounds in
 of_device_uevent at addr ffff8800091b4c49

On Sat, May 28, 2016 at 09:12:34AM +0200, Wolfram Sang wrote:
> > 0day kernel testing robot got the below dmesg and the first bad commit is
> > 
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> 
> So, I got a success message from buildbot "[wsa:i2c/for-next]
> 72a71f869c95dc11b73f09fe18c593d4a0618c3f BUILD SUCCESS".
> 
> I assume now that the above message covers only compile-testing while

That's right. "BUILD SUCCESS" only covers compile testing and static
checks.

> linus master tree also gets boot testing? Correct?

All branches will get boot testing. linus/master naturally receives
much more tests since all branches are eventually based on some Linus
commit.

> I was under the impression before that the above message also covers
> simple boot tests.

There will be simple boot tests quickly after the compile tests.
However boot tests typically need more time to be detected, bisected
and especially manual checked. We are yet to automate more boot error
reports.

Thanks,
Fengguang