[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+55aFwZpMB=VUTCNUgc4dcCEy9_T4iE0R0pAfDets=zDFJunQ@mail.gmail.com>
Date: Fri, 23 Mar 2018 13:50:39 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Eric Biggers <ebiggers3@...il.com>
Cc: Dmitry Vyukov <dvyukov@...gle.com>,
LKML <linux-kernel@...r.kernel.org>,
syzkaller <syzkaller@...glegroups.com>
Subject: Re: syzbot dashboard
On Fri, Mar 23, 2018 at 1:16 PM, Eric Biggers <ebiggers3@...il.com> wrote:
>
> A compromise could be to remove the raw.log from the emails, and send the config
> in 'defconfig' format rather than the full config
I really don't think the config is very legible, and isn't something
that people will look at to judge whether it's intrresting or not.
It's still "many hundreds of lines of line noise"
And it shouldn't really be part of the consideration whether a bug is
really worth looking at or not anyway, although *after* you've found
the bug as a developer, you may decide "ok, that configuration isn't
valid, so I should just disallow it in Kconfig". But that's still a
bugfix.
So I think the config can stay purely on the web (for when you go "so
how do I *reproduce* this?") along with the actual reproducer and the
full logs.
I'd rather make the emails be small and legible, and contain the
minimum amount of information.
Because I really do *not* need a few hundred emails from some
automated source that each have a roughly thousand-line config
attachements.
An email with 50 lines of THE ACTUAL DECODED OOPS? Sure. That's
critical information. That doesn't make me go "why does this stupid
bot spew garbage at me"?
Linus
Powered by blists - more mailing lists