Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752816AbeADLSE (ORCPT + 1 other); Thu, 4 Jan 2018 06:18:04 -0500 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:57875 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752159AbeADLSD (ORCPT ); Thu, 4 Jan 2018 06:18:03 -0500 Date: Thu, 4 Jan 2018 12:18:01 +0100 From: Pavel Machek To: Dmitry Vyukov Cc: Mike Galbraith , LKML , Greg Kroah-Hartman , Andrew Morton , Linus Torvalds , syzkaller Subject: Re: LKML admins (syzbot emails are not delivered) Message-ID: <20180104111801.GA2220@amd> References: <20180104092552.GA991@amd> <1515058705.7875.25.camel@gmx.de> <20180104095628.GA4407@atrey.karlin.mff.cuni.cz> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ikeVEW9yuYc//A+q" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: --ikeVEW9yuYc//A+q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu 2018-01-04 12:09:26, Dmitry Vyukov wrote: > On Thu, Jan 4, 2018 at 10:56 AM, Pavel Machek wrote: > >> 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 th= ey > >> > > 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/1GzamOm= RAwAJ > >> > > > >> > > "general protection fault in __wake_up_common" > >> > > https://groups.google.com/d/msg/syzkaller-bugs/4TrrZ0bIViw/rBcYLUJ= HAgAJ > >> > > > >> > > Does anybody know how to get in contact with real people behind LK= ML > >> > > 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. >=20 >=20 > Hi Pavel, >=20 > I've answered this question here in full detail. In short, this is > useful and actionable. > https://groups.google.com/d/msg/syzkaller/2nVn_XkVhEE/GjjfISejCgAJ I've already deleted many such reports from my lkml folder. It definitely is below quality of normal bug reports. You want all the credit while doing none of the work: This bug is generated by a dumb bot. It may contain errors. See https://goo.gl/tpsmEJ for details. Direct all questions to syzk...@googlegroups.com. Please credit me with: Reported-by: syzbot =2E.. #syz invalid Note: if the crash happens again, it will cause creation of a new bug report. I'd say this belongs to separate list. Interested parties can subscribe, and you can still manually forward reports if you handle duplicities etc. Pavel --=20 (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blo= g.html --ikeVEW9yuYc//A+q Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlpODWkACgkQMOfwapXb+vJl3wCePoIAD2OGl+ZmotFZFWDvIFhK oE0AnR4vQ9N1NwJ78Sq6PL953YA2jvv0 =0cQS -----END PGP SIGNATURE----- --ikeVEW9yuYc//A+q--