From: Christoph Hellwig <hch@lst.de>
To: cem@kernel.org
Cc: linux-xfs@vger.kernel.org, hch@lst.de, dlemoal@kernel.org
Subject: Re: [PATCH 1/4] xfs: factor out isize updates from xfs_dio_write_end_io
Date: Tue, 10 Mar 2026 13:52:51 +0100 [thread overview]
Message-ID: <20260310125251.GA3323@lst.de> (raw)
In-Reply-To: <20260310115555.114197-2-cem@kernel.org>
On Tue, Mar 10, 2026 at 12:55:04PM +0100, cem@kernel.org wrote:
> +static int
> +xfs_dio_endio_set_isize(
> + struct inode *inode,
> + loff_t offset,
> + ssize_t size)
> +{
> + struct xfs_inode *ip = XFS_I(inode);
> +
> + if (offset + size <= i_size_read(inode))
> + return 0;
> +
> + spin_lock(&ip->i_flags_lock);
> + if (offset + size > i_size_read(inode)) {
> + i_size_write(inode, offset + size);
> + spin_unlock(&ip->i_flags_lock);
> + } else {
> + spin_unlock(&ip->i_flags_lock);
> + }
> +
> + return xfs_setfilesize(ip, offset, size);
This now calls xfs_setfilesize for the case where we don't update
the inode size. This looks harmless to be, but isn't needed.
This should become something like:
if (offset + size <= i_size_read(inode)) {
spin_unlock(&ip->i_flags_lock);
return 0;
}
i_size_write(inode, offset + size);
spin_unlock(&ip->i_flags_lock);
return xfs_setfilesize(ip, offset, size);
next prev parent reply other threads:[~2026-03-10 12:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 11:55 [PATCH 0/4] Zoned device cleanups cem
2026-03-10 11:55 ` [PATCH 1/4] xfs: factor out isize updates from xfs_dio_write_end_io cem
2026-03-10 12:51 ` Damien Le Moal
2026-03-10 12:52 ` Christoph Hellwig [this message]
2026-03-10 11:55 ` [PATCH 2/4] xfs: move zoned dio ioend to its own function cem
2026-03-10 12:53 ` Christoph Hellwig
2026-03-10 12:54 ` Damien Le Moal
2026-03-10 11:55 ` [PATCH 3/4] xfs: factor out xfs_zone_inc_written cem
2026-03-10 12:54 ` Christoph Hellwig
2026-03-10 12:55 ` Damien Le Moal
2026-03-10 11:55 ` [PATCH 4/4] xfs: opencode xfs_zone_record_blocks cem
2026-03-10 12:54 ` Christoph Hellwig
2026-03-10 12:56 ` Damien Le Moal
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=20260310125251.GA3323@lst.de \
--to=hch@lst.de \
--cc=cem@kernel.org \
--cc=dlemoal@kernel.org \
--cc=linux-xfs@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.