linux-ext4 - Re: [PATCH] ext4: Don't run ext4lazyinit for read-only filesystems

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: <166431556706.3511882.3840047540179825060.b4-ty@mit.edu>
Date:   Tue, 27 Sep 2022 17:53:34 -0400
From:   "Theodore Ts'o" <tytso@....edu>
To:     adilger.kernel@...ger.ca, josh@...htriplett.org
Cc:     "Theodore Ts'o" <tytso@....edu>, linux-ext4@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ext4: Don't run ext4lazyinit for read-only filesystems

On Sun, 31 Jul 2022 20:24:53 -0700, Josh Triplett wrote:
> On a read-only filesystem, we won't invoke the block allocator, so we
> don't need to prefetch the block bitmaps.
> 
> This avoids starting and running the ext4lazyinit thread at all on a
> system with no read-write ext4 filesystems (for instance, a container VM
> with read-only filesystems underneath an overlayfs).
> 
> [...]

Applied, thanks!

[1/1] ext4: Don't run ext4lazyinit for read-only filesystems
      commit: 3490a40364962a2599bc5a8126003a47150b84d3

Best regards,
-- 
Theodore Ts'o <tytso@....edu>