From: Christoph Hellwig <hch@lst.de>
To: Chandan Babu R <chandan.babu@oracle.com>,
"Darrick J. Wong" <djwong@kernel.org>
Cc: linux-xfs@vger.kernel.org
Subject: iext handling fixes and cleanup v2
Date: Thu, 2 May 2024 09:33:52 +0200 [thread overview]
Message-ID: <20240502073355.1893587-1-hch@lst.de> (raw)
Hi all,
this series fixes two unlikely to hit iext handling bugs in
xfs_reflink_end_cow and then cleanups up the iext count updgrade
handling.
It has been split from a larger series that needs more work.
Changes since v1:
- rename xfs_iext_count_ensure to xfs_iext_count_extend
Diffstat:
libxfs/xfs_attr.c | 5 ----
libxfs/xfs_bmap.c | 5 ----
libxfs/xfs_inode_fork.c | 57 +++++++++++++++++++++---------------------------
libxfs/xfs_inode_fork.h | 6 +----
xfs_bmap_item.c | 4 ---
xfs_bmap_util.c | 23 ++++---------------
xfs_dquot.c | 5 ----
xfs_iomap.c | 9 +------
xfs_reflink.c | 23 +++++--------------
xfs_rtalloc.c | 5 ----
10 files changed, 45 insertions(+), 97 deletions(-)
next reply other threads:[~2024-05-02 7:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 7:33 Christoph Hellwig [this message]
2024-05-02 7:33 ` [PATCH 1/3] xfs: upgrade the extent counters in xfs_reflink_end_cow_extent later Christoph Hellwig
2024-05-02 7:33 ` [PATCH 2/3] xfs: remove a racy if_bytes check in xfs_reflink_end_cow_extent Christoph Hellwig
2024-05-02 7:33 ` [PATCH 3/3] xfs: simplify iext overflow checking and upgrade Christoph Hellwig
2024-05-02 7:55 ` Dave Chinner
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=20240502073355.1893587-1-hch@lst.de \
--to=hch@lst.de \
--cc=chandan.babu@oracle.com \
--cc=djwong@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).