From: Eric Biggers <ebiggers3@gmail.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
syzkaller <syzkaller@googlegroups.com>
Subject: Re: syzbot dashboard
Date: Fri, 23 Mar 2018 13:16:34 -0700 [thread overview]
Message-ID: <20180323201634.GA16350@gmail.com> (raw)
In-Reply-To: <CACT4Y+YDqJMb4mC6c--Ku=ZL9MpELmUKMXe4uQJ6H0av2FJC9w@mail.gmail.com>
On Thu, Mar 22, 2018 at 10:45:43AM +0100, 'Dmitry Vyukov' via syzkaller wrote:
> On Wed, Mar 21, 2018 at 9:32 PM, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> > On Wed, Mar 21, 2018 at 9:11 AM, Dmitry Vyukov <dvyukov@google.com> wrote:
> >>
> >> syzkaller/syzbot dashboard is now live at:
> >> https://syzkaller.appspot.com
> >
> > Ok, this may well be the thing that makes syzbot reports useful, if
> > they point to an external report instead of sending an absolutely huge
> > illegible email that nobody can read.
>
> The dashboard was initially meant to be used only for internal
> monitoring (communication with kernel developers over emails) and I am
> too close to the project to see obvious stuff. So thanks for the
> feedback!
>
> Do you mean to replace all attachments in syzbot emails with links to
> web dashboard content?
> I've heard opinions both ways (including "I am not clicking on any
> external links, include all content in the email"). So we need to
> decide. Provided that lots of email clients seem to inline
> attachments, rather than show them as separate files, I am leaning
> towards providing just links. Then emails can be short and tidy. Also
> will solve the problem of "I don't see original attachments in your
> forwarded email".
>
A compromise could be to remove the raw.log from the emails, and send the config
in 'defconfig' format rather than the full config; that trims it down from 5256
lines to 925 currently. That would get rid of most of what is bloating the size
of the emails, while still keeping the (very useful) C and syzkaller
reproducers. Dashboard would still have everything, of course.
Eric
next prev parent reply other threads:[~2018-03-23 20:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-21 16:11 syzbot dashboard Dmitry Vyukov
2018-03-21 20:32 ` Linus Torvalds
2018-03-22 9:45 ` Dmitry Vyukov
2018-03-22 22:20 ` Linus Torvalds
2018-03-23 20:16 ` Eric Biggers [this message]
2018-03-23 20:50 ` Linus Torvalds
2018-03-26 8:46 ` Dmitry Vyukov
2018-04-14 18:25 ` Linus Torvalds
2018-04-16 11:15 ` Dmitry Vyukov
2018-04-16 15:55 ` Randy Dunlap
2018-04-18 18:33 ` Dmitry Vyukov
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=20180323201634.GA16350@gmail.com \
--to=ebiggers3@gmail.com \
--cc=dvyukov@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller@googlegroups.com \
--cc=torvalds@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.