Linux EXT4 FS development
 help / color / mirror / Atom feed
From: Luis Henriques <lhenriques@suse.de>
To: Jan Kara <jack@suse.cz>
Cc: Ted Tso <tytso@mit.edu>,  <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] ext4: Avoid excessive credit estimate in ext4_tmpfile()
Date: Fri, 08 Mar 2024 11:26:12 +0000	[thread overview]
Message-ID: <87v85xrmln.fsf@suse.de> (raw)
In-Reply-To: <20240307115320.28949-1-jack@suse.cz> (Jan Kara's message of "Thu, 7 Mar 2024 12:53:20 +0100")

Jan Kara <jack@suse.cz> writes:

> A user with minimum journal size (1024 blocks these days) complained
> about the following error triggered by generic/697 test in
> ext4_tmpfile():
>
> run fstests generic/697 at 2024-02-28 05:34:46
> JBD2: vfstest wants too many credits credits:260 rsv_credits:0 max:256
> EXT4-fs error (device loop0) in __ext4_new_inode:1083: error 28
>
> Indeed the credit estimate in ext4_tmpfile() is huge.
> EXT4_MAXQUOTAS_INIT_BLOCKS() is 219, then 10 credits from ext4_tmpfile()
> itself and then ext4_xattr_credits_for_new_inode() adds more credits
> needed for security attributes and ACLs. Now the
> EXT4_MAXQUOTAS_INIT_BLOCKS() is in fact unnecessary because we've
> already initialized quotas with dquot_init() shortly before and so
> EXT4_MAXQUOTAS_TRANS_BLOCKS() is enough (which boils down to 3 credits).
>
> Fixes: af51a2ac36d1 ("ext4: ->tmpfile() support")
> Signed-off-by: Jan Kara <jack@suse.cz>

FWIW, I've run generic/697 with a 1GiB device, with a block size of 65536.
Without this patch the test fails.  Feel free to add my

Tested-by: Luis Henriques <lhenriques@suse.de>

Cheers,
-- 
Luís

> ---
>  fs/ext4/namei.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/ext4/namei.c b/fs/ext4/namei.c
> index 05b647e6bc19..58fee3c6febc 100644
> --- a/fs/ext4/namei.c
> +++ b/fs/ext4/namei.c
> @@ -2898,7 +2898,7 @@ static int ext4_tmpfile(struct mnt_idmap *idmap, struct inode *dir,
>  	inode = ext4_new_inode_start_handle(idmap, dir, mode,
>  					    NULL, 0, NULL,
>  					    EXT4_HT_DIR,
> -			EXT4_MAXQUOTAS_INIT_BLOCKS(dir->i_sb) +
> +			EXT4_MAXQUOTAS_TRANS_BLOCKS(dir->i_sb) +
>  			  4 + EXT4_XATTR_TRANS_BLOCKS);
>  	handle = ext4_journal_current_handle();
>  	err = PTR_ERR(inode);
> -- 
>
> 2.35.3
>

  reply	other threads:[~2024-03-08 12:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-07 11:53 [PATCH] ext4: Avoid excessive credit estimate in ext4_tmpfile() Jan Kara
2024-03-08 11:26 ` Luis Henriques [this message]
2024-03-08 13:11 ` Disha Goel
2024-05-02 20:00 ` 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=87v85xrmln.fsf@suse.de \
    --to=lhenriques@suse.de \
    --cc=jack@suse.cz \
    --cc=linux-ext4@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