public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Josh Triplett <josh@joshtriplett.org>
To: Lukas Czerner <lczerner@redhat.com>
Cc: Theodore Ts'o <tytso@mit.edu>,
	Andreas Dilger <adilger.kernel@dilger.ca>,
	linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ext4: Don't run ext4lazyinit for read-only filesystems
Date: Thu, 1 Sep 2022 00:09:04 +0200	[thread overview]
Message-ID: <Yw/cANWSlKYqiT9L@localhost> (raw)
In-Reply-To: <20220803070001.iygdreewgveotfwx@fedora>

On Wed, Aug 03, 2022 at 09:00:01AM +0200, Lukas Czerner wrote:
> On Sun, Jul 31, 2022 at 08:24:53PM -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).
> > 
> > Fixes: 21175ca434c5 ("ext4: make prefetch_block_bitmaps default")
> > Signed-off-by: Josh Triplett <josh@joshtriplett.org>
> > ---
> 
> Looks good to me.
> 
> Reviewed-by: Lukas Czerner <lczerner@redhat.com>
> 
> > Tested in a VM, with a read-only ext4 root filesystem. Confirmed that
> > ext4lazyinit starts without this patch, and does not start with this
> > patch.
> > 
> > (For a future merge window, not the current one. Please let me know if I
> > need to re-send this at a later, more convenient time.)

Now that the merge window has been closed for a while, I wanted to
follow up on this to see if it could get into next.

> >  fs/ext4/super.c | 6 +++---
> >  1 file changed, 3 insertions(+), 3 deletions(-)
> > 
> > diff --git a/fs/ext4/super.c b/fs/ext4/super.c
> > index 845f2f8aee5f..20437acc8865 100644
> > --- a/fs/ext4/super.c
> > +++ b/fs/ext4/super.c
> > @@ -3973,9 +3973,9 @@ int ext4_register_li_request(struct super_block *sb,
> >  		goto out;
> >  	}
> >  
> > -	if (test_opt(sb, NO_PREFETCH_BLOCK_BITMAPS) &&
> > -	    (first_not_zeroed == ngroups || sb_rdonly(sb) ||
> > -	     !test_opt(sb, INIT_INODE_TABLE)))
> > +	if (sb_rdonly(sb) ||
> > +	    (test_opt(sb, NO_PREFETCH_BLOCK_BITMAPS) &&
> > +	     (first_not_zeroed == ngroups || !test_opt(sb, INIT_INODE_TABLE))))
> >  		goto out;
> >  
> >  	elr = ext4_li_request_new(sb, first_not_zeroed);
> > -- 
> > 2.36.1
> > 
> 

  reply	other threads:[~2022-08-31 22:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-01  3:24 [PATCH] ext4: Don't run ext4lazyinit for read-only filesystems Josh Triplett
2022-08-03  7:00 ` Lukas Czerner
2022-08-31 22:09   ` Josh Triplett [this message]
2022-09-27 21:53 ` Theodore Ts'o

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Yw/cANWSlKYqiT9L@localhost \
    --to=josh@joshtriplett.org \
    --cc=adilger.kernel@dilger.ca \
    --cc=lczerner@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox