From: Jan Kara <jack@suse.cz>
To: libaokun@huaweicloud.com
Cc: linux-ext4@vger.kernel.org, tytso@mit.edu,
adilger.kernel@dilger.ca, jack@suse.cz, ritesh.list@gmail.com,
linux-kernel@vger.kernel.org, yi.zhang@huawei.com,
yangerkun@huawei.com, Baokun Li <libaokun1@huawei.com>
Subject: Re: [PATCH 2/2] ext4: propagate errors from ext4_sb_bread() in ext4_xattr_block_cache_find()
Date: Mon, 6 May 2024 22:40:23 +0200 [thread overview]
Message-ID: <20240506204023.l74kejvjlinufuei@quack3> (raw)
In-Reply-To: <20240504075526.2254349-3-libaokun@huaweicloud.com>
On Sat 04-05-24 15:55:26, libaokun@huaweicloud.com wrote:
> From: Baokun Li <libaokun1@huawei.com>
>
> In ext4_xattr_block_cache_find(), when ext4_sb_bread() returns an error,
> we will either continue to find the next ea block or return NULL to try to
> insert a new ea block. But whether ext4_sb_bread() returns -EIO or -ENOMEM,
> the next operation is most likely to fail with the same error. So propagate
> the error returned by ext4_sb_bread() to make ext4_xattr_block_set() fail
> to reduce pointless operations.
>
> Signed-off-by: Baokun Li <libaokun1@huawei.com>
Looks good. Feel free to add:
Reviewed-by: Jan Kara <jack@suse.cz>
Honza
> ---
> fs/ext4/xattr.c | 25 ++++++++++++++-----------
> 1 file changed, 14 insertions(+), 11 deletions(-)
>
> diff --git a/fs/ext4/xattr.c b/fs/ext4/xattr.c
> index 9fdd13422073..11742e1f16d7 100644
> --- a/fs/ext4/xattr.c
> +++ b/fs/ext4/xattr.c
> @@ -2059,8 +2059,13 @@ ext4_xattr_block_set(handle_t *handle, struct inode *inode,
>
> inserted:
> if (!IS_LAST_ENTRY(s->first)) {
> - new_bh = ext4_xattr_block_cache_find(inode, header(s->base),
> - &ce);
> + new_bh = ext4_xattr_block_cache_find(inode, header(s->base), &ce);
> + if (IS_ERR(new_bh)) {
> + error = PTR_ERR(new_bh);
> + new_bh = NULL;
> + goto cleanup;
> + }
> +
> if (new_bh) {
> /* We found an identical block in the cache. */
> if (new_bh == bs->bh)
> @@ -3090,8 +3095,8 @@ ext4_xattr_cmp(struct ext4_xattr_header *header1,
> *
> * Find an identical extended attribute block.
> *
> - * Returns a pointer to the block found, or NULL if such a block was
> - * not found or an error occurred.
> + * Returns a pointer to the block found, or NULL if such a block was not
> + * found, or an error pointer if an error occurred while reading ea block.
> */
> static struct buffer_head *
> ext4_xattr_block_cache_find(struct inode *inode,
> @@ -3113,13 +3118,11 @@ ext4_xattr_block_cache_find(struct inode *inode,
>
> bh = ext4_sb_bread(inode->i_sb, ce->e_value, REQ_PRIO);
> if (IS_ERR(bh)) {
> - if (PTR_ERR(bh) == -ENOMEM) {
> - mb_cache_entry_put(ea_block_cache, ce);
> - return NULL;
> - }
> - bh = NULL;
> - EXT4_ERROR_INODE(inode, "block %lu read error",
> - (unsigned long)ce->e_value);
> + if (PTR_ERR(bh) != -ENOMEM)
> + EXT4_ERROR_INODE(inode, "block %lu read error",
> + (unsigned long)ce->e_value);
> + mb_cache_entry_put(ea_block_cache, ce);
> + return bh;
> } else if (ext4_xattr_cmp(header, BHDR(bh)) == 0) {
> *pce = ce;
> return bh;
> --
> 2.39.2
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2024-05-06 20:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-04 7:55 [PATCH 0/2] ext4: fix WARNING in mb_cache_destroy libaokun
2024-05-04 7:55 ` [PATCH 1/2] ext4: fix mb_cache_entry's e_refcnt leak in ext4_xattr_block_cache_find() libaokun
2024-05-06 20:37 ` Jan Kara
2024-05-04 7:55 ` [PATCH 2/2] ext4: propagate errors from ext4_sb_bread() " libaokun
2024-05-06 20:40 ` Jan Kara [this message]
2024-05-07 23:03 ` [PATCH 0/2] ext4: fix WARNING in mb_cache_destroy 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=20240506204023.l74kejvjlinufuei@quack3 \
--to=jack@suse.cz \
--cc=adilger.kernel@dilger.ca \
--cc=libaokun1@huawei.com \
--cc=libaokun@huaweicloud.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ritesh.list@gmail.com \
--cc=tytso@mit.edu \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
/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