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: <20250429144615.GE25655@frogsfrogsfrogs>
Date: Tue, 29 Apr 2025 07:46:15 -0700
From: "Darrick J. Wong" <djwong@...nel.org>
To: John Zakrzewski <jozakrzewski@...rosoft.com>
Cc: "linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>
Subject: Re: Question about fsck for ext4

On Tue, Apr 29, 2025 at 01:25:35PM +0000, John Zakrzewski wrote:
> Hi! We are using the k8 utils opensource
> project(https://github.com/kubernetes/utils) and looking for your
> thoughts on an issue where fsck is being run on every remount and if
> this is necessary for journaling filesystems.  Eric Sandeen's comments
> here(https://github.com/kubernetes/utils/pull/132#issuecomment-605492335)
> indicate it is not but wanted to verify with you that his statements
> apply to ext4 as well.  Ultimately I am looking for reassurance to
> relax the need for fsck on mounts for ext4.  I look forward to hearing
> your thoughts and please don't hesitate to ask clarifying questions.
> Thank you!

Running fsck on any journalled filesystem shouldn't be necessary if
they've stopped the practice of snapshotting unfrozen filesystems.

But these days, maybe you /want/ to run fsck in dryrun mode to detect
maliciously corrupt filesystem images before mounting them?

--D

> John Zakrzewski
> Software Engineer
> Azure Core
> jozakrzewski@...rosoft.com
> 

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ