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
| ||
|
Message-ID: <3c541015-d5c3-b80a-8795-a6d783af3cd5@urbanec.net> Date: Sat, 16 Apr 2022 00:29:15 +1000 From: Peter Urbanec <linux-ext4.vger.kernel.org@...anec.net> To: linux-ext4@...r.kernel.org Subject: Re: resize2fs on ext4 leads to corruption On 16/04/2022 00:16, Peter Urbanec wrote: > In light of recent mailing list traffic, I suspect that the issue may > be caused by sparse_super2 . Or perhaps not. It seems that issue mentioned on the list was specific to online resize, whereas I was attempting an offline resize. Another difference is that in my case the operation appears to have completed without any reported errors or warnings on the command line or in dmesg. Just silent data corruption. I am hoping that the resize is reversible and that the change in size from 3,906,946,560 blocks to 5,860,419,840 blocks did not cause 32-bit overflows or wraparounds that would result in overwriting data. Peter
Powered by blists - more mailing lists