[lkml]   [2018]   [Jan]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: what trees/branches to test on syzbot
On Fri, Jan 19, 2018 at 2:48 AM, Fengguang Wu <> wrote:
> Hi Dmitry,
> On Tue, Jan 16, 2018 at 10:58:51AM +0100, Dmitry Vyukov wrote:
>> On Tue, Jan 16, 2018 at 10:45 AM, Guenter Roeck <> wrote:
>>> On Mon, Jan 15, 2018 at 11:51 PM, Dmitry Vyukov <>
>>> wrote:
>>>> Hello,
>>>> Several people proposed that linux-next should not be tested on
>>>> syzbot. While some people suggested that it needs to test as many
>>>> trees as possible. I've initially included linux-next as it is a
>>>> staging area before upstream tree, with the intention that patches are
>>>> _tested_ there, is they are not tested there, bugs enter upstream
>>>> tree. And then it takes much longer to get fix into other trees.
>>>> So the question is: what trees/branches should be tested? Preferably
>>>> in priority order as syzbot can't test all of them.
>>> I always thought that -next existed specifically to give people a
>>> chance to test the code in it. Maybe the question is where to report
>>> the test results ?
>> FTR, from Guenter on another thread:
>>> Interesting. Assuming that refers to linux-next, not linux-net, that
>>> may explain why linux-next tends to deteriorate. I wonder if I should
>>> drop it from my testing as well. I'll be happy to follow whatever the
>>> result of this exchange is and do the same.
>> If we agree on some list of important branches, and what branches
>> specifically should not be tested with automatic reporting, I think it
>> will benefit everybody.
>> +Fengguang, can you please share your list and rationale behind it?
> 0-day aims to aggressively test as much tree and branches as possible,
> including various developer trees, maintainer, linux-next, mainline and
> stable trees. Here are the complete list of 800+ trees we monitored:
> The rationale is obvious. IMHO what really matters here is about
> capability rather than rationale: that policy heavily relies on the
> fundamental capability of auto bisecting. Once regressions are
> bisected, we know the owners of problem to auto send report to, ie.
> the first bad commit's author and committer.
> For the bugs that cannot be bisected, they tend to be old ones and
> we report more often on mainline tree than linux-next.

Thanks for the info, Fengguang.

Bisecting is something we need to syzbot in future. However about 50%
of syzbot bugs are due to races and are somewhat difficult to bisect

 \ /
  Last update: 2018-01-22 14:35    [W:0.077 / U:14.972 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site