lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CACT4Y+aG1JEkLfFvvBhC0ZSpk-huWwAshdb8nwKExFbw2fq59Q@mail.gmail.com>
Date:   Fri, 5 Mar 2021 16:18:46 +0100
From:   Dmitry Vyukov <dvyukov@...gle.com>
To:     Pavel Machek <pavel@....cz>
Cc:     bobwxc <bobwxc@...il.cn>, LKML <linux-kernel@...r.kernel.org>
Subject: Re: syzbot reporting less duplicates

On Wed, Feb 3, 2021 at 8:24 PM Pavel Machek <pavel@....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@...il.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 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.

This is now implemented and deployed:
https://github.com/google/syzkaller/pull/2472

Here is the first example report with the prefix:
https://lore.kernel.org/lkml/0000000000002592aa05bccabae5@google.com/T/#u

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ