From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753358AbeADViN (ORCPT + 1 other); Thu, 4 Jan 2018 16:38:13 -0500 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:46829 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753287AbeADViM (ORCPT ); Thu, 4 Jan 2018 16:38:12 -0500 Date: Thu, 4 Jan 2018 22:38:10 +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: <20180104213810.GA18699@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="KsGdsel6WgEHnImy" 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: --KsGdsel6WgEHnImy 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 Unfortantely, some of the reports are making it to the lkml. 200KB each! Due to attached .config files. I believe you should not be spamming lkml in the first place. If you insist on sending to lkml and list admins are okay with that, please gzip the config file. Pavel > do_syscall_32_irqs_on arch/x86/entry/common.c:327 [inline] > do_fast_syscall_32+0x3ee/0xf9d arch/x86/entry/common.c:389 > entry_SYSENTER_compat+0x54/0x63 arch/x86/entry/entry_64_compat.S:129 Looks like the same bug I sent out a fix for yesterday. #syz fix: capabilities: fix buffer overread on very short xattr https://marc.info/?l=3Dlinux-kernel&m=3D151488700301705 --=20 (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blo= g.html --KsGdsel6WgEHnImy Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlpOnsIACgkQMOfwapXb+vJVpwCdHsO7t8zAxg1MQpl3KpDFwidy lckAn3m4IkVvkLPPslUM39mLV2MM6bhr =oJD9 -----END PGP SIGNATURE----- --KsGdsel6WgEHnImy--