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

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] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 31 Jul 2023 18:01:14 +0800
From:   Qu Wenruo <quwenruo.btrfs@....com>
To:     Christoph Hellwig <hch@...radead.org>
Cc:     Christoph Hellwig <hch@....de>,
        syzbot <syzbot+ae97a827ae1c3336bbb4@...kaller.appspotmail.com>,
        clm@...com, dsterba@...e.com, johannes.thumshirn@....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 prepare_to_merge



On 2023/7/31 17:46, Christoph Hellwig wrote:
> Thanks.  I've not been able to reproduce it on the apparent bisection
> commit for more than half an hour, but running it on the originally
> reported commit reproduces it after a few minutes.  I'll see if I
> can come up with a better bisection.
>

I checked the related code, and didn't find anything obvious.

But there is a chance that the image is intentionally corrupted so that
we got a reloc root but incorrect root owner.

Thus I sent out a patch to make that triggering ASSERT() to a more
graceful exit:

https://lore.kernel.org/linux-btrfs/24881cc9caf738f6248232709d7357d3186773b5.1690782754.git.wqu@suse.com/T/#u

Although I never got the C reproducer to trigger, thus no confirmation
on that.

Thanks,
Qu