From: syzbot <syzbot+b9d2e54d2301324657ed@syzkaller.appspotmail.com>
To: clm@fb.com, djwong@kernel.org, dsterba@suse.com,
fdmanana@suse.com, josef@toxicpanda.com,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [btrfs?] kernel BUG in set_state_bits
Date: Sat, 21 Jan 2023 06:15:22 -0800 [thread overview]
Message-ID: <000000000000eedc4705f2c6cba6@google.com> (raw)
In-Reply-To: <0000000000000e082305eec34072@google.com>
syzbot has bisected this issue to:
commit 05fd9564e9faf0f23b4676385e27d9405cef6637
Author: Darrick J. Wong <djwong@kernel.org>
Date: Mon Mar 14 17:55:32 2022 +0000
btrfs: fix fallocate to use file_modified to update permissions consistently
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17db2ab6480000
start commit: 296a7b7eb792 Merge tag 'for-linus' of git://git.armlinux.o..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=143b2ab6480000
console output: https://syzkaller.appspot.com/x/log.txt?x=103b2ab6480000
kernel config: https://syzkaller.appspot.com/x/.config?x=4edf421741552bc3
dashboard link: https://syzkaller.appspot.com/bug?extid=b9d2e54d2301324657ed
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12ec2ab7880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14dc4613880000
Reported-by: syzbot+b9d2e54d2301324657ed@syzkaller.appspotmail.com
Fixes: 05fd9564e9fa ("btrfs: fix fallocate to use file_modified to update permissions consistently")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-01-21 14:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 12:20 [syzbot] kernel BUG in set_state_bits syzbot
2022-12-11 5:17 ` syzbot
2023-01-21 14:15 ` syzbot [this message]
2024-08-06 19:25 ` [syzbot] [btrfs?] " syzbot
2024-08-06 22:18 ` Darrick J. Wong
2024-08-06 22:18 ` syzbot
2024-08-07 11:33 ` David Sterba
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=000000000000eedc4705f2c6cba6@google.com \
--to=syzbot+b9d2e54d2301324657ed@syzkaller.appspotmail.com \
--cc=clm@fb.com \
--cc=djwong@kernel.org \
--cc=dsterba@suse.com \
--cc=fdmanana@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).