From: Pavel Machek <pavel@ucw.cz>
To: Mike Galbraith <efault@gmx.de>
Cc: Dmitry Vyukov <dvyukov@google.com>,
LKML <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
syzkaller <syzkaller@googlegroups.com>
Subject: Re: LKML admins (syzbot emails are not delivered)
Date: Thu, 4 Jan 2018 10:56:28 +0100 [thread overview]
Message-ID: <20180104095628.GA4407@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <1515058705.7875.25.camel@gmx.de>
> On Thu, 2018-01-04 at 10:25 +0100, Pavel Machek wrote:
> > Hi!
> > >
> > > Some of syzbot emails don't appear on LKML mailing lists, while they
> > > were mailed as any other emails. Here are few examples:
> > >
> > > "KASAN: use-after-free Read in rds_tcp_dev_event"
> > > https://groups.google.com/d/msg/syzkaller-bugs/nEeIAsNLWL4/1GzamOmRAwAJ
> > >
> > > "general protection fault in __wake_up_common"
> > > https://groups.google.com/d/msg/syzkaller-bugs/4TrrZ0bIViw/rBcYLUJHAgAJ
> > >
> > > Does anybody know how to get in contact with real people behind LKML
> > > and/or bugzilla?
> >
> > Not delivering syzbot emails might be good thing?
>
> Nah, the thing is finding and reporting bugs just like a human would,
> it just doesn't need sleep etc, so sometimes reports more than humans
> can keep up with. It needs a smarter brother.. but then again, maybe
> not, if bots start fixing things too, a lot of meatware hackers would
> have to go find real jobs.
Sending random, unrepeatable Oopses to lkml is not what humans would
do, and perhaps not something bots should do, either.
> > You claimed you generate so many of them that you can't even check
> > them by hand, so what makes you think thousands of lkml readers want
> > to delete them by hand?
>
> Mail filters have existed for untold ages :)
Yeah, well, spammers also existed for long long time :-).
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2018-01-04 9:56 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-04 9:09 Dmitry Vyukov
2018-01-04 9:23 ` Greg Kroah-Hartman
2018-01-04 9:56 ` Ozgur
2018-01-04 15:31 ` David Miller
2018-01-04 19:11 ` Ozgur
2018-01-04 11:03 ` Dmitry Vyukov
2018-01-04 11:04 ` Dmitry Vyukov
2018-01-04 11:20 ` Greg Kroah-Hartman
2018-01-04 15:35 ` David Miller
2018-01-15 9:43 ` Dmitry Vyukov
2018-03-01 16:22 ` Dmitry Vyukov
2018-03-08 20:03 ` David Miller
2018-03-12 8:56 ` Dmitry Vyukov
2018-03-12 14:03 ` David Miller
2018-01-04 23:50 ` Theodore Ts'o
2018-01-08 12:01 ` Dmitry Vyukov
2018-01-08 12:11 ` Dmitry Vyukov
2018-01-04 9:25 ` Pavel Machek
2018-01-04 9:38 ` Mike Galbraith
2018-01-04 9:56 ` Pavel Machek [this message]
2018-01-04 11:09 ` Dmitry Vyukov
2018-01-04 11:18 ` Pavel Machek
2018-01-15 10:08 ` Dmitry Vyukov
2018-01-15 13:08 ` Pavel Machek
2018-01-15 13:38 ` Dmitry Vyukov
2018-01-15 13:53 ` Pavel Machek
2018-01-04 15:23 ` Eric W. Biederman
2018-01-15 10:54 ` Dmitry Vyukov
2018-01-15 12:54 ` Pavel Machek
2018-01-15 13:02 ` Dmitry Vyukov
2018-01-15 16:16 ` Eric W. Biederman
2018-01-16 18:01 ` Dmitry Vyukov
2018-01-15 16:38 ` Eric W. Biederman
2018-01-16 7:12 ` Theodore Ts'o
2018-01-16 7:51 ` Dmitry Vyukov
2018-01-16 9:52 ` Guenter Roeck
2018-01-16 9:56 ` Dmitry Vyukov
2018-01-16 9:58 ` Guenter Roeck
2018-01-16 7:59 ` Dmitry Vyukov
2018-01-16 11:19 ` Fengguang Wu
2018-01-16 8:31 ` Dmitry Vyukov
2018-01-16 23:13 ` Theodore Ts'o
2018-01-17 8:06 ` Dmitry Vyukov
2018-01-17 16:53 ` Theodore Ts'o
2018-01-17 17:16 ` Dmitry Vyukov
2018-01-17 22:27 ` Bernd Petrovitsch
2018-01-16 8:34 ` Dmitry Vyukov
2018-01-24 16:04 ` Alan Cox
2018-01-24 17:06 ` Eric W. Biederman
2018-01-24 17:32 ` Greg Kroah-Hartman
2018-01-16 18:20 ` Dmitry Vyukov
2018-01-17 8:13 ` Dmitry Vyukov
2018-01-04 21:38 ` Pavel Machek
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=20180104095628.GA4407@atrey.karlin.mff.cuni.cz \
--to=pavel@ucw.cz \
--cc=akpm@linux-foundation.org \
--cc=dvyukov@google.com \
--cc=efault@gmx.de \
--cc=gregkh@linuxfoundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®