From: Pavel Machek <pavel@ucw.cz>
To: syzbot <syzbot+5ecbe63baca437585bd4@syzkaller.appspotmail.com>,
syzkaller@googlegroups.com
Cc: len.brown@intel.com, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org, rjw@rjwysocki.net,
syzkaller-bugs@googlegroups.com
Subject: syzbot spam -- is it useful? time to ban them from the list? [was Re: kernel BUG in memory_bm_free]
Date: Wed, 3 Feb 2021 14:38:29 +0100 [thread overview]
Message-ID: <20210203133829.GA5952@duo.ucw.cz> (raw)
In-Reply-To: <0000000000009c21de05ba6849e7@google.com>
[-- Attachment #1: Type: text/plain, Size: 1074 bytes --]
On Tue 2021-02-02 21:59:17, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 3aaf0a27 Merge tag 'clang-format-for-linux-v5.11-rc7' of g..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=17ef6108d00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=10152c2ea16351e7
> dashboard link: https://syzkaller.appspot.com/bug?extid=5ecbe63baca437585bd4
> userspace arch: arm64
>
> Unfortunately, I don't have any reproducer for this issue yet.
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+5ecbe63baca437585bd4@syzkaller.appspotmail.com
Important: Follow netiquette. You are sending automated emails to people
that did not consent to it. You are not even providing unsubscribe
link. That's actually illegal here.
Put real name of person responsible in the email. Put [syzbot] in the
subject so that it and any resulting replies can be filtered out.
Pavel
--
http://www.livejournal.com/~pavelmachek
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2021-02-03 13:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-03 5:59 kernel BUG in memory_bm_free syzbot
2021-02-03 13:38 ` Pavel Machek [this message]
2021-03-15 7:08 ` Dmitry Vyukov
2021-03-15 12:09 ` Catalin Marinas
2021-03-15 12:26 ` Dmitry Vyukov
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=20210203133829.GA5952@duo.ucw.cz \
--to=pavel@ucw.cz \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=syzbot+5ecbe63baca437585bd4@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=syzkaller@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