From: "Darrick J. Wong" <djwong@kernel.org>
To: Leah Rumancik <leah.rumancik@gmail.com>
Cc: linux-xfs@vger.kernel.org, amir73il@gmail.com,
chandan.babu@oracle.com, fred@cloudflare.com,
mngyadam@amazon.com
Subject: Re: [PATCH 6.1 CANDIDATE 00/24] more backport proposals for linux-6.1.y
Date: Fri, 26 Apr 2024 16:14:07 -0700 [thread overview]
Message-ID: <20240426231407.GQ360919@frogsfrogsfrogs> (raw)
In-Reply-To: <20240426215512.2673806-1-leah.rumancik@gmail.com>
On Fri, Apr 26, 2024 at 02:54:47PM -0700, Leah Rumancik wrote:
> Hi again,
>
> These have been tested on 10 configs x 30 runs of the auto group. No
> regressions were seen.
>
> - Leah
>
> Darrick J. Wong (8):
> xfs: fix incorrect error-out in xfs_remove
> xfs: invalidate block device page cache during unmount
> xfs: attach dquots to inode before reading data/cow fork mappings
> xfs: hoist refcount record merge predicates
> xfs: estimate post-merge refcounts correctly
> xfs: invalidate xfs_bufs when allocating cow extents
> xfs: allow inode inactivation during a ro mount log recovery
> xfs: fix log recovery when unknown rocompat bits are set
>
> Dave Chinner (10):
> xfs: write page faults in iomap are not buffered writes
> xfs: punching delalloc extents on write failure is racy
> xfs: use byte ranges for write cleanup ranges
> xfs,iomap: move delalloc punching to iomap
> iomap: buffered write failure should not truncate the page cache
> xfs: xfs_bmap_punch_delalloc_range() should take a byte range
> iomap: write iomap validity checks
> xfs: use iomap_valid method to detect stale cached iomaps
> xfs: drop write error injection is unfixable, remove it
> xfs: fix off-by-one-block in xfs_discard_folio()
>
> Eric Sandeen (1):
> xfs: short circuit xfs_growfs_data_private() if delta is zero
>
> Guo Xuenan (2):
> xfs: wait iclog complete before tearing down AIL
> xfs: fix super block buf log item UAF during force shutdown
>
> Hironori Shiina (1):
> xfs: get root inode correctly at bulkstat
>
> Long Li (2):
> xfs: fix sb write verify for lazysbcount
> xfs: fix incorrect i_nlink caused by inode racing
Looks good to me,
Acked-by: Darrick J. Wong <djwong@kernel.org>
--D
>
> fs/iomap/buffered-io.c | 254 ++++++++++++++++++++++++++++++++++-
> fs/iomap/iter.c | 19 ++-
> fs/xfs/libxfs/xfs_bmap.c | 8 +-
> fs/xfs/libxfs/xfs_errortag.h | 12 +-
> fs/xfs/libxfs/xfs_refcount.c | 146 +++++++++++++++++---
> fs/xfs/libxfs/xfs_sb.c | 7 +-
> fs/xfs/xfs_aops.c | 37 ++---
> fs/xfs/xfs_bmap_util.c | 10 +-
> fs/xfs/xfs_bmap_util.h | 2 +-
> fs/xfs/xfs_buf.c | 1 +
> fs/xfs/xfs_buf_item.c | 2 +
> fs/xfs/xfs_error.c | 27 +++-
> fs/xfs/xfs_file.c | 2 +-
> fs/xfs/xfs_fsops.c | 4 +
> fs/xfs/xfs_icache.c | 6 +
> fs/xfs/xfs_inode.c | 16 ++-
> fs/xfs/xfs_ioctl.c | 4 +-
> fs/xfs/xfs_iomap.c | 177 ++++++++++++++----------
> fs/xfs/xfs_iomap.h | 6 +-
> fs/xfs/xfs_log.c | 53 ++++----
> fs/xfs/xfs_mount.c | 15 +++
> fs/xfs/xfs_pnfs.c | 6 +-
> include/linux/iomap.h | 47 +++++--
> 23 files changed, 683 insertions(+), 178 deletions(-)
>
> --
> 2.44.0.769.g3c40516874-goog
>
>
prev parent reply other threads:[~2024-04-26 23:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 21:54 [PATCH 6.1 CANDIDATE 00/24] more backport proposals for linux-6.1.y Leah Rumancik
2024-04-26 21:54 ` [PATCH 6.1 CANDIDATE 01/24] xfs: write page faults in iomap are not buffered writes Leah Rumancik
2024-04-26 21:54 ` [PATCH 6.1 CANDIDATE 02/24] xfs: punching delalloc extents on write failure is racy Leah Rumancik
2024-04-26 21:54 ` [PATCH 6.1 CANDIDATE 03/24] xfs: use byte ranges for write cleanup ranges Leah Rumancik
2024-04-26 21:54 ` [PATCH 6.1 CANDIDATE 04/24] xfs,iomap: move delalloc punching to iomap Leah Rumancik
2024-04-26 21:54 ` [PATCH 6.1 CANDIDATE 05/24] iomap: buffered write failure should not truncate the page cache Leah Rumancik
2024-04-26 21:54 ` [PATCH 6.1 CANDIDATE 06/24] xfs: xfs_bmap_punch_delalloc_range() should take a byte range Leah Rumancik
2024-04-26 21:54 ` [PATCH 6.1 CANDIDATE 07/24] iomap: write iomap validity checks Leah Rumancik
2024-04-26 21:54 ` [PATCH 6.1 CANDIDATE 08/24] xfs: use iomap_valid method to detect stale cached iomaps Leah Rumancik
2024-04-26 21:54 ` [PATCH 6.1 CANDIDATE 09/24] xfs: drop write error injection is unfixable, remove it Leah Rumancik
2024-04-26 21:54 ` [PATCH 6.1 CANDIDATE 10/24] xfs: fix off-by-one-block in xfs_discard_folio() Leah Rumancik
2024-04-26 21:54 ` [PATCH 6.1 CANDIDATE 11/24] xfs: fix incorrect error-out in xfs_remove Leah Rumancik
2024-04-26 21:54 ` [PATCH 6.1 CANDIDATE 12/24] xfs: fix sb write verify for lazysbcount Leah Rumancik
2024-04-26 21:55 ` [PATCH 6.1 CANDIDATE 13/24] xfs: fix incorrect i_nlink caused by inode racing Leah Rumancik
2024-04-26 21:55 ` [PATCH 6.1 CANDIDATE 14/24] xfs: invalidate block device page cache during unmount Leah Rumancik
2024-04-26 21:55 ` [PATCH 6.1 CANDIDATE 15/24] xfs: attach dquots to inode before reading data/cow fork mappings Leah Rumancik
2024-04-26 21:55 ` [PATCH 6.1 CANDIDATE 16/24] xfs: wait iclog complete before tearing down AIL Leah Rumancik
2024-04-26 21:55 ` [PATCH 6.1 CANDIDATE 17/24] xfs: fix super block buf log item UAF during force shutdown Leah Rumancik
2024-04-26 21:55 ` [PATCH 6.1 CANDIDATE 18/24] xfs: hoist refcount record merge predicates Leah Rumancik
2024-04-26 21:55 ` [PATCH 6.1 CANDIDATE 19/24] xfs: estimate post-merge refcounts correctly Leah Rumancik
2024-04-26 21:55 ` [PATCH 6.1 CANDIDATE 20/24] xfs: invalidate xfs_bufs when allocating cow extents Leah Rumancik
2024-04-26 21:55 ` [PATCH 6.1 CANDIDATE 21/24] xfs: allow inode inactivation during a ro mount log recovery Leah Rumancik
2024-04-26 21:55 ` [PATCH 6.1 CANDIDATE 22/24] xfs: fix log recovery when unknown rocompat bits are set Leah Rumancik
2024-04-26 21:55 ` [PATCH 6.1 CANDIDATE 23/24] xfs: get root inode correctly at bulkstat Leah Rumancik
2024-04-26 21:55 ` [PATCH 6.1 CANDIDATE 24/24] xfs: short circuit xfs_growfs_data_private() if delta is zero Leah Rumancik
2024-04-26 23:14 ` Darrick J. Wong [this message]
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=20240426231407.GQ360919@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=amir73il@gmail.com \
--cc=chandan.babu@oracle.com \
--cc=fred@cloudflare.com \
--cc=leah.rumancik@gmail.com \
--cc=linux-xfs@vger.kernel.org \
--cc=mngyadam@amazon.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).