From: syzbot <syzbot+2a0fbd1cb355de983130@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, hch@lst.de,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
liushixin2@huawei.com, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [fs?] WARNING in brelse
Date: Fri, 04 Aug 2023 17:09:27 -0700 [thread overview]
Message-ID: <00000000000094fcb0060221d31a@google.com> (raw)
In-Reply-To: <000000000000f1a26f05e9a72f57@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=15e8976da80000
start commit: 77856d911a8c Merge tag 'arm64-fixes' of git://git.kernel.o..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=17e8976da80000
console output: https://syzkaller.appspot.com/x/log.txt?x=13e8976da80000
kernel config: https://syzkaller.appspot.com/x/.config?x=f967143badd2fa39
dashboard link: https://syzkaller.appspot.com/bug?extid=2a0fbd1cb355de983130
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11393ab3880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12a2a99d880000
Reported-by: syzbot+2a0fbd1cb355de983130@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
prev parent reply other threads:[~2023-08-05 0:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 11:45 [syzbot] WARNING in brelse syzbot
2023-08-05 0:09 ` syzbot [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=00000000000094fcb0060221d31a@google.com \
--to=syzbot+2a0fbd1cb355de983130@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liushixin2@huawei.com \
--cc=syzkaller-bugs@googlegroups.com \
--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 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).