linux-kernel - Re: [syzbot] [btrfs?] kernel BUG in __extent_writepage

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20240515163645.GR4449@suse.cz>
Date: Wed, 15 May 2024 18:36:45 +0200
From: David Sterba <dsterba@...e.cz>
To: syzbot <syzbot+06006fc4a90bff8e8f17@...kaller.appspotmail.com>
Cc: clm@...com, dsterba@...e.com, josef@...icpanda.com,
	linux-btrfs@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [btrfs?] kernel BUG in __extent_writepage_io

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@...kaller.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.