linux-kernel - RE: ext4 damage suspected in between 5.15.167

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]

Message-ID: <229641a5c7f046b282c151cb1c6b9110@AcuMS.aculab.com>
Date: Mon, 16 Dec 2024 15:16:00 +0000
From: David Laight <David.Laight@...LAB.COM>
To: 'Nikolai Zhubr' <zhubr.2@...il.com>, Theodore Ts'o <tytso@....edu>
CC: "linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>,
	"stable@...r.kernel.org" <stable@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "jack@...e.cz"
	<jack@...e.cz>
Subject: RE: ext4 damage suspected in between 5.15.167 - 5.15.170

....
> > The location of block allocation bitmaps never gets changed, so this
> > sort of thing only happens due to hardware-induced corruption.
> 
> Well, unless e.g. some modified sectors start being flushed to random
> wrong offsets, like in [1] above, or something similar.

Or cutting the power in the middle of SSD 'wear levelling'.

I've seen a completely trashed disk (sectors in completely the
wrong places) after an unexpected power cut.

	David

-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)