From: syzbot <syzbot+9ce4a36127ca92b59677@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 insert_state_fast
Date: Thu, 05 Jan 2023 11:31:19 -0800 [thread overview]
Message-ID: <000000000000686d3405f1895819@google.com> (raw)
In-Reply-To: <000000000000a2432a05eea26be6@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=14ef1870480000
start commit: 644e9524388a Merge tag 'for-v6.1-rc' of git://git.kernel.o..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=16ef1870480000
console output: https://syzkaller.appspot.com/x/log.txt?x=12ef1870480000
kernel config: https://syzkaller.appspot.com/x/.config?x=8d01b6e3197974dd
dashboard link: https://syzkaller.appspot.com/bug?extid=9ce4a36127ca92b59677
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12806381880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=127f33c5880000
Reported-by: syzbot+9ce4a36127ca92b59677@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-05 19:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 21:10 [syzbot] kernel BUG in insert_state_fast syzbot
2023-01-05 19:31 ` syzbot [this message]
2024-09-09 2:47 ` [syzbot] [btrfs?] " syzbot
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=000000000000686d3405f1895819@google.com \
--to=syzbot+9ce4a36127ca92b59677@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