linux-kernel - Re: [GIT PULL] Btrfs fixes for 6.8-rc2

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: <cbd72a58-6d6b-4e78-8028-63e92ad9502c@gmx.com>
Date: Sat, 27 Jan 2024 08:35:39 +1030
From: Qu Wenruo <quwenruo.btrfs@....com>
To: Linus Torvalds <torvalds@...ux-foundation.org>, Qu Wenruo <wqu@...e.com>
Cc: dsterba@...e.cz, David Sterba <dsterba@...e.com>,
 linux-btrfs@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] Btrfs fixes for 6.8-rc2



On 2024/1/27 08:32, Linus Torvalds wrote:
> On Fri, 26 Jan 2024 at 13:56, Qu Wenruo <wqu@...e.com> wrote:
>>
>> On 2024/1/27 08:21, Linus Torvalds wrote:
>>>
>>> Allocation lifetime problems?
>>
>> Could be, thus it may be better to output the flags of the first page
>> for tree-checker.
>
> Note that the fact that it magically went away certainly implies that
> it never "really" existed, and that something was using a pointer or
> similar.
>
> IOW, this is not some IO that got scribbled over, or a cache that got
> corrupted. If it had been real corruption, I would have expected that
> it would have stayed around in memory.

Yep, thus it makes sense to show the page status of an eb.

It could be some race that the eb pages are not properly hold, thus its
content changed unexpectedly.

Thanks,
Qu

>
>                   Linus
>