From: David Sterba <dsterba@suse.cz>
To: syzbot <syzbot+06006fc4a90bff8e8f17@syzkaller.appspotmail.com>
Cc: clm@fb.com, dsterba@suse.com, 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?] kernel BUG in __extent_writepage_io
Date: Wed, 15 May 2024 18:36:45 +0200 [thread overview]
Message-ID: <20240515163645.GR4449@suse.cz> (raw)
In-Reply-To: <000000000000169326060971d07a@google.com>
On Sun, Nov 05, 2023 at 05:31:27PM -0800, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 8bc9e6515183 Merge tag 'devicetree-for-6.7' of git://git.k..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=10e087a0e80000
> kernel config: https://syzkaller.appspot.com/x/.config?x=c3aadb4391bbacce
> dashboard link: https://syzkaller.appspot.com/bug?extid=06006fc4a90bff8e8f17
> compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
>
> Unfortunately, I don't have any reproducer for this issue yet.
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/6c9b9f6781b1/disk-8bc9e651.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/44acae63a945/vmlinux-8bc9e651.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/f0058df8ab69/bzImage-8bc9e651.xz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+06006fc4a90bff8e8f17@syzkaller.appspotmail.com
#syz fix: btrfs: don't drop extent_map for free space inode on write error
We were not aware that syzbot also hit the problem, we got report from
our CI so the auto close tags was missing.
prev parent reply other threads:[~2024-05-15 16:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 1:31 [syzbot] [btrfs?] kernel BUG in __extent_writepage_io syzbot
2023-12-13 1:58 ` syzbot
2023-12-13 19:15 ` syzbot
2024-05-15 16:36 ` David Sterba [this message]
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=20240515163645.GR4449@suse.cz \
--to=dsterba@suse.cz \
--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=syzbot+06006fc4a90bff8e8f17@syzkaller.appspotmail.com \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).