From: syzbot <syzbot+404b4b745080b6210c6c@syzkaller.appspotmail.com>
To: dhowells@redhat.com, dmantipov@yandex.ru, jlayton@kernel.org,
joannelkoong@gmail.com, josef@toxicpanda.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
lvc-project@linuxtesting.org, miklos@szeredi.hu,
mszeredi@redhat.com, netfs@lists.linux.dev,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [netfs?] kernel BUG in iov_iter_revert (2)
Date: Sat, 30 Nov 2024 06:44:03 -0800 [thread overview]
Message-ID: <674b24b3.050a0220.253251.00dd.GAE@google.com> (raw)
In-Reply-To: <67238110.050a0220.35b515.015e.GAE@google.com>
syzbot has bisected this issue to:
commit 3b97c3652d9128ab7f8c9b8adec6108611fdb153
Author: Joanne Koong <joannelkoong@gmail.com>
Date: Thu Oct 24 17:18:08 2024 +0000
fuse: convert direct io to use folios
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13e29f78580000
start commit: f486c8aa16b8 Add linux-next specific files for 20241128
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=10129f78580000
console output: https://syzkaller.appspot.com/x/log.txt?x=17e29f78580000
kernel config: https://syzkaller.appspot.com/x/.config?x=e348a4873516af92
dashboard link: https://syzkaller.appspot.com/bug?extid=404b4b745080b6210c6c
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=131f71e8580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12bc200f980000
Reported-by: syzbot+404b4b745080b6210c6c@syzkaller.appspotmail.com
Fixes: 3b97c3652d91 ("fuse: convert direct io to use folios")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-11-30 14:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 13:07 [syzbot] [netfs?] kernel BUG in iov_iter_revert (2) syzbot
2024-11-30 14:44 ` syzbot [this message]
2024-12-04 13:59 ` David Howells
2024-12-04 14:20 ` syzbot
2024-12-04 14:11 ` David Howells
2024-12-04 14:39 ` syzbot
2024-12-04 14:43 ` David Howells
2024-12-05 9:38 ` David Howells
2024-12-05 9:59 ` 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=674b24b3.050a0220.253251.00dd.GAE@google.com \
--to=syzbot+404b4b745080b6210c6c@syzkaller.appspotmail.com \
--cc=dhowells@redhat.com \
--cc=dmantipov@yandex.ru \
--cc=jlayton@kernel.org \
--cc=joannelkoong@gmail.com \
--cc=josef@toxicpanda.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=miklos@szeredi.hu \
--cc=mszeredi@redhat.com \
--cc=netfs@lists.linux.dev \
--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