From: syzbot <syzbot+adec8406ad17413d4c06@syzkaller.appspotmail.com>
To: axboe@kernel.dk, christophe.leroy@csgroup.eu, clm@fb.com,
dsterba@suse.com, josef@toxicpanda.com,
linux-btrfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, mpe@ellerman.id.au,
npiggin@gmail.com, shuah@kernel.org,
syzkaller-bugs@googlegroups.com, torvalds@linux-foundation.org,
ye.xingchen@zte.com.cn
Subject: Re: [syzbot] [btrfs?] WARNING in btrfs_free_reserved_data_space_noquota
Date: Tue, 01 Aug 2023 02:27:22 -0700 [thread overview]
Message-ID: <00000000000083e9d60601d927a0@google.com> (raw)
In-Reply-To: <000000000000fac82605ee97fb72@google.com>
syzbot suspects this issue was fixed by commit:
commit 487c20b016dc48230367a7be017f40313e53e3bd
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Thu Mar 30 21:53:51 2023 +0000
iov: improve copy_iovec_from_user() code generation
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17cfdf19a80000
start commit: 4bdec23f971b Merge tag 'hwmon-for-v6.3-rc4' of git://git.k..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=acdb62bf488a8fe5
dashboard link: https://syzkaller.appspot.com/bug?extid=adec8406ad17413d4c06
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11bf8bcec80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=153d4f75c80000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: iov: improve copy_iovec_from_user() code generation
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-08-01 9:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 8:43 [syzbot] WARNING in btrfs_free_reserved_data_space_noquota syzbot
2022-11-30 10:35 ` Michael Ellerman
2023-08-01 9:27 ` syzbot [this message]
2024-05-16 15:38 ` 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=00000000000083e9d60601d927a0@google.com \
--to=syzbot+adec8406ad17413d4c06@syzkaller.appspotmail.com \
--cc=axboe@kernel.dk \
--cc=christophe.leroy@csgroup.eu \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=shuah@kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=torvalds@linux-foundation.org \
--cc=ye.xingchen@zte.com.cn \
/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).