From: Al Viro <viro@zeniv.linux.org.uk>
To: syzbot <syzbot+7902cd7684bc35306224@syzkaller.appspotmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] WARNING in __brelse
Date: Sat, 1 Oct 2022 23:50:39 +0100 [thread overview]
Message-ID: <YzjEP8639prhhCKe@ZenIV> (raw)
In-Reply-To: <000000000000d2adfa05e9c2d0b9@google.com>
On Wed, Sep 28, 2022 at 01:43:39PM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 46452d3786a8 Merge tag 'sound-6.0-rc8' of git://git.kernel..
> git tree: upstream
> console+strace: https://syzkaller.appspot.com/x/log.txt?x=154595ef080000
> kernel config: https://syzkaller.appspot.com/x/.config?x=755695d26ad09807
> dashboard link: https://syzkaller.appspot.com/bug?extid=7902cd7684bc35306224
> compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=127543c4880000
For crying out loud... Seeing that it has
syz_mount_image$udf(
in it and seeing that MAINTAINERS has
UDF FILESYSTEM
M: Jan Kara <jack@suse.com>
S: Maintained
F: Documentation/filesystems/udf.rst
F: fs/udf/
which word is missing in Subject and which mail is missing in Cc?
"[syzbot] WARNING in __brelse" says nothing beyond "it's probably about
something that does buffer_head IO". Recepients of that mail have no way
to find which fs is involved without wget of your reproducer and looking
into it (well, that or start a browser, cut'n'paste the URL there, etc.).
You, OTOH, have that information from the very beginning...
prev parent reply other threads:[~2022-10-01 22:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 20:43 [syzbot] WARNING in __brelse syzbot
2022-10-01 22:50 ` Al Viro [this message]
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=YzjEP8639prhhCKe@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+7902cd7684bc35306224@syzkaller.appspotmail.com \
--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).