From: Dmitry Vyukov <dvyukov@google.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: bobwxc <bobwxc@email.cn>, LKML <linux-kernel@vger.kernel.org>,
syzkaller <syzkaller@googlegroups.com>
Subject: Re: syzbot reporting less duplicates
Date: Wed, 10 Feb 2021 12:27:38 +0100 [thread overview]
Message-ID: <CACT4Y+ZrnDTCE0umuE0i2Sb+=Acszgc9k_hXopMX_kCkE4YQrQ@mail.gmail.com> (raw)
In-Reply-To: <20210203192453.GA21047@amd>
On Wed, Feb 3, 2021 at 8:24 PM Pavel Machek <pavel@ucw.cz> wrote:
>
> Hi!
> On Wed 2021-02-03 19:22:34, Dmitry Vyukov wrote:
> > On Wed, Feb 3, 2021 at 6:39 PM bobwxc <bobwxc@email.cn> wrote:
> > >
> > > On Wed, Feb 03, 2021 at 05:05:43PM +0100, Pavel Machek wrote:
> > > > On Mon 2021-02-01 11:52:12, Dmitry Vyukov wrote:
> > > > Could we please get common prefix (like syzbot: KASAN:....) so that
> > > > the bulk of emails is easier to remove?
> > > There are several bots testing on the kernel, maybe we should give a prefix
> > > format for all bot.
> > > Also we can use mail-address to fliter email, but it's still a little
> > > inconvenient.
> >
> > Hi Pavel, bobwxc,
> >
> > Yes, I was wondering if syzbot in From/To/CC can be used for
> > filtering? I assume email clients that can filter based on subject can
> > also filter based on From/To/CC.
> > Does anybody filter syzbot emails? Maybe you can share what works
> > best?
>
> From does not really work. So... syzbot reports for subsystems I don't
> maintain are uninteresting, and so is the resulting discussion.
>
> While filtering on "From:" is easy for initial report, it does not
> make it easy to remove follow up discussion.n
I've filed https://github.com/google/syzkaller/issues/2435 to track
the subject feature request.
I thought that maybe filtering based on From/To/CC should work right
away, it should capture follow up discussions as well.
> > I am not sure a common prefix for all bots is useful because it
> > supports only all or nothing. There are also some bots that
> > maintainers use now that seem to be fundamental to the process, if one
> > is ignoring them, then they are effectively ignoring what the
> > maintainer is saying.
>
> I'm pretty sure common prefix for all bots is useful.
>
> Best regards,
> Pavel
> --
> http://www.livejournal.com/~pavelmachek
next prev parent reply other threads:[~2021-02-10 11:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 10:52 syzbot reporting less duplicates Dmitry Vyukov
2021-02-03 16:05 ` Pavel Machek
2021-02-03 17:28 ` bobwxc
2021-02-03 18:22 ` Dmitry Vyukov
2021-02-03 19:24 ` Pavel Machek
2021-02-10 11:27 ` Dmitry Vyukov [this message]
2021-03-05 15:18 ` 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='CACT4Y+ZrnDTCE0umuE0i2Sb+=Acszgc9k_hXopMX_kCkE4YQrQ@mail.gmail.com' \
--to=dvyukov@google.com \
--cc=bobwxc@email.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=syzkaller@googlegroups.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;
as well as URLs for NNTP newsgroup(s).