From: Pavel Machek <pavel@ucw.cz>
To: linux-rtc@vger.kernel.org,
Alessandro Zummo <a.zummo@towertech.it>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: Reminder: 1 open syzbot bug in rtc subsystem
Date: Sun, 28 Jul 2019 15:23:33 +0200 [thread overview]
Message-ID: <20190728132332.GB8718@xo-6d-61-c0.localdomain> (raw)
In-Reply-To: <20190724025008.GL643@sol.localdomain>
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.
Pavel
next prev parent reply other threads:[~2019-07-28 13:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 2:50 Reminder: 1 open syzbot bug in rtc subsystem Eric Biggers
2019-07-28 13:23 ` Pavel Machek [this message]
2019-07-31 2:27 ` Eric Biggers
2019-08-02 10:24 ` Pavel Machek
2019-07-31 2:33 ` Eric Biggers
-- strict thread matches above, loose matches on Subject: below --
2019-07-02 5:10 Eric Biggers
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=20190728132332.GB8718@xo-6d-61-c0.localdomain \
--to=pavel@ucw.cz \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/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;
as well as URLs for NNTP newsgroup(s).