From: syzbot <syzbot+9992306148b06272f3bb@syzkaller.appspotmail.com>
To: axboe@kernel.dk, brauner@kernel.org, clm@fb.com,
dhowells@redhat.com, dsterba@suse.com, dsterba@suse.cz,
hch@lst.de, josef@toxicpanda.com, linux-btrfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [btrfs?] WARNING in emit_fiemap_extent
Date: Sat, 29 Jul 2023 14:45:30 -0700 [thread overview]
Message-ID: <000000000000be8b800601a71d81@google.com> (raw)
In-Reply-To: <00000000000091164305fe966bdd@google.com>
syzbot suspects this issue was fixed by commit:
commit aa3dbde878961dd333cdd3c326b93e6c84a23ed4
Author: David Howells <dhowells@redhat.com>
Date: Mon May 22 13:49:54 2023 +0000
splice: Make splice from an O_DIRECT fd use copy_splice_read()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14dc6319a80000
start commit: 40f71e7cd3c6 Merge tag 'net-6.4-rc7' of git://git.kernel.o..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=7ff8f87c7ab0e04e
dashboard link: https://syzkaller.appspot.com/bug?extid=9992306148b06272f3bb
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10c65e87280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1094a78b280000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: splice: Make splice from an O_DIRECT fd use copy_splice_read()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-07-29 21:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 21:34 [syzbot] [btrfs?] WARNING in emit_fiemap_extent syzbot
2023-06-21 12:33 ` David Sterba
2023-07-29 21:45 ` syzbot [this message]
2023-08-02 14:46 ` Aleksandr Nogikh
2024-05-16 15:04 ` David Sterba
2024-05-16 15:08 ` 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=000000000000be8b800601a71d81@google.com \
--to=syzbot+9992306148b06272f3bb@syzkaller.appspotmail.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=clm@fb.com \
--cc=dhowells@redhat.com \
--cc=dsterba@suse.com \
--cc=dsterba@suse.cz \
--cc=hch@lst.de \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@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).