linux-kernel - Re: [syzbot] WARNING in _

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <YzjEP8639prhhCKe@ZenIV>
Date:   Sat, 1 Oct 2022 23:50:39 +0100
From:   Al Viro <viro@...iv.linux.org.uk>
To:     syzbot <syzbot+7902cd7684bc35306224@...kaller.appspotmail.com>
Cc:     linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
        syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] WARNING in __brelse

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@...e.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...