linux-kernel - Re: 6.6.8 stable: crash in folio_mark

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 for Android: free password hash cracker in your pocket

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

Message-ID: <ZZHWFOJln4I1A0sd@casper.infradead.org>
Date: Sun, 31 Dec 2023 20:59:00 +0000
From: Matthew Wilcox <willy@...radead.org>
To: Genes Lists <lists@...ience.com>
Cc: linux-kernel@...r.kernel.org, Andrew Morton <akpm@...ux-foundation.org>,
	linux-fsdevel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: 6.6.8 stable: crash in folio_mark_dirty

On Sat, Dec 30, 2023 at 10:23:26AM -0500, Genes Lists wrote:
> Apologies in advance, but I cannot git bisect this since machine was
> running for 10 days on 6.6.8 before this happened.

This problem simply doesn't make sense.  There's just no way we shoud be
able to get a not-uptodate folio into the page tables.  We do have one
pending patch which fixes a situation in which we can get some very
odd-looking situations due to reusing a page which has been freed.
I appreciate your ability to reproduce this is likely nil, but if you
could add

https://lore.kernel.org/all/20231220214715.912B4C433CA@smtp.kernel.org/

to your kernel, it might make things more stable for you.