From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9BC03C32750 for ; Wed, 31 Jul 2019 02:27:10 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 6A9552089E for ; Wed, 31 Jul 2019 02:27:10 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1564540030; bh=gCQs/AJpjE78ozD3C46eDnktCWUrIqq9DV4zAvc5v4A=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=euadF3hNIrumMQUfUjXdA8TWbcqHzEzI38u+zPkbk7bZ40tW76iObxCHvLszO5p/b mHda4+G0YVtnpX9IwT+AsL/9phZmzSxwGGk70NJ19nzr2m9M33DYhkZ5EE7if9nCvi vfP1EndTPKuABtvAgv9jS8Pmn8MhtAELbMFp+NqQ= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726492AbfGaC1K (ORCPT ); Tue, 30 Jul 2019 22:27:10 -0400 Received: from mail.kernel.org ([198.145.29.99]:58930 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725877AbfGaC1J (ORCPT ); Tue, 30 Jul 2019 22:27:09 -0400 Received: from sol.localdomain (c-24-5-143-220.hsd1.ca.comcast.net [24.5.143.220]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 4427F206E0; Wed, 31 Jul 2019 02:27:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1564540029; bh=gCQs/AJpjE78ozD3C46eDnktCWUrIqq9DV4zAvc5v4A=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=RQYJoPd0SLF/+0dRdSIT0yrq9zvfPqCNl1YYzurfgFnqfAqhmlcTAqEFiIfmfDvBC AjF3llS0aMnuqOPIxclnFzb92maCefQrqHXRgw3Bo/9Hq05rh4hSwQiOYjql04jj/1 hXM/NsFAbR0KDCHq0ojutoRVveQ7Q3B80VKT4knM= Date: Tue, 30 Jul 2019 19:27:07 -0700 From: Eric Biggers To: Pavel Machek Cc: linux-rtc@vger.kernel.org, Alessandro Zummo , Alexandre Belloni , linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com Subject: Re: Reminder: 1 open syzbot bug in rtc subsystem Message-ID: <20190731022707.GC687@sol.localdomain> Mail-Followup-To: Pavel Machek , linux-rtc@vger.kernel.org, Alessandro Zummo , Alexandre Belloni , linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com References: <20190724025008.GL643@sol.localdomain> <20190728132332.GB8718@xo-6d-61-c0.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190728132332.GB8718@xo-6d-61-c0.localdomain> User-Agent: Mutt/1.12.1 (2019-06-15) Sender: linux-rtc-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-rtc@vger.kernel.org On Sun, Jul 28, 2019 at 03:23:33PM +0200, Pavel Machek wrote: > On Tue 2019-07-23 19:50:08, Eric Biggers wrote: > > [This email was generated by a script. Let me know if you have any suggestions > > to make it better, or if you want it re-generated with the latest status.] > > > > Of the currently open syzbot reports against the upstream kernel, I've manually > > marked 1 of them as possibly being a bug in the rtc subsystem. > > > > If you believe this bug is no longer valid, please close the syzbot report by > > sending a '#syz fix', '#syz dup', or '#syz invalid' command in reply to the > > original thread, as explained at https://goo.gl/tpsmEJ#status > > > > If you believe I misattributed this bug to the rtc subsystem, please let me > > know, and if possible forward the report to the correct people or mailing list. > > > > Here is the bug: > > > Can you stop spamming lkml? > > Sending 20 "reminders" in a row is not something human would do, and it is not > something your bot should be allowed to do, either. > Hi Pavel, just to clarify, though I used a script to generate these emails, I manually reviewed and sent each one; I also manually assigned the subsystems and sanity checked the bisection results. (I'm also not on the syzbot team. I just care about the security and reliability of the Linux kernel...) The reason there are so many of these emails is that there are a lot of kernel subsystems with open bug reports, many clearly still valid -- even considering that I decided to skip some subsystems after deciding to just fix the bugs myself, update the bug statuses myself, send some other email, or just wait. I suppose there's some argument to be made that it's too noisy to Cc linux-kernel when I've already assigned a subsystem, though, so I'll try dropping linux-kernel from Cc for next time and just using the subsystem list and maintainers, and see if that goes any better or worse. Note that the syzbot reports themselves are still going to linux-kernel, though. Thanks! - Eric