From: syzbot <syzbot+9743a41f74f00e50fc77@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, brauner@kernel.org, hch@infradead.org,
hch@lst.de, jack@suse.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, liushixin2@huawei.com,
nogikh@google.com, syzkaller-bugs@googlegroups.com,
tytso@mit.edu, viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [udf] WARNING in invalidate_bh_lru
Date: Sat, 03 Jun 2023 10:35:29 -0700 [thread overview]
Message-ID: <00000000000081d40a05fd3d18ed@google.com> (raw)
In-Reply-To: <000000000000eccdc505f061d47f@google.com>
syzbot has bisected this issue to:
commit f6e2c20ca7604e6a267c93a511d19dda72573be1
Author: Liu Shixin <liushixin2@huawei.com>
Date: Fri Apr 29 21:38:04 2022 +0000
fs: sysv: check sbi->s_firstdatazone in complete_read_super
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13eed371280000
start commit: 4ecd704a4c51 tpm, tpm_tis: correct tpm_tis_flags enumerati..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=101ed371280000
console output: https://syzkaller.appspot.com/x/log.txt?x=17eed371280000
kernel config: https://syzkaller.appspot.com/x/.config?x=162cf2103e4a7453
dashboard link: https://syzkaller.appspot.com/bug?extid=9743a41f74f00e50fc77
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16ebf8c9280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12df6ab6280000
Reported-by: syzbot+9743a41f74f00e50fc77@syzkaller.appspotmail.com
Fixes: f6e2c20ca760 ("fs: sysv: check sbi->s_firstdatazone in complete_read_super")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-06-03 17:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 2:57 [syzbot] [sysv?] [vfs?] WARNING in invalidate_bh_lru syzbot
2023-04-30 6:40 ` Theodore Ts'o
2023-04-30 6:40 ` syzbot
2023-04-30 16:12 ` Theodore Ts'o
2023-05-01 9:18 ` Aleksandr Nogikh
2023-05-03 4:31 ` Theodore Ts'o
2023-06-03 17:35 ` syzbot [this message]
2024-03-02 12:14 ` [syzbot] [udf] " syzbot
2024-03-11 9:32 ` Jan Kara
2025-10-14 14:33 ` Tetsuo Handa
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=00000000000081d40a05fd3d18ed@google.com \
--to=syzbot+9743a41f74f00e50fc77@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=jack@suse.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liushixin2@huawei.com \
--cc=nogikh@google.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.