From: Fengguang Wu <fengguang.wu@intel.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Erico Nunes <erico.nunes@datacom.ind.br>, LKP <lkp@01.org>,
linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org,
Ye Xiaolong <xiaolong.ye@intel.com>
Subject: Re: [i2c: dev] d6760b14d4: BUG: KASAN: slab-out-of-bounds in of_device_uevent at addr ffff8800091b4c49
Date: Sat, 28 May 2016 15:24:33 +0800 [thread overview]
Message-ID: <20160528072433.GA1844@wfg-t540p.sh.intel.com> (raw)
In-Reply-To: <20160528071234.GA1714@katana>
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
next prev parent reply other threads:[~2016-05-28 7:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-28 6:30 [i2c: dev] d6760b14d4: BUG: KASAN: slab-out-of-bounds in of_device_uevent at addr ffff8800091b4c49 kernel test robot
2016-05-28 7:12 ` Wolfram Sang
2016-05-28 7:24 ` Fengguang Wu [this message]
2016-05-28 7:32 ` Wolfram Sang
2016-05-28 10:14 ` Fengguang Wu
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=20160528072433.GA1844@wfg-t540p.sh.intel.com \
--to=fengguang.wu@intel.com \
--cc=erico.nunes@datacom.ind.br \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=wsa@the-dreams.de \
--cc=xiaolong.ye@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