public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Catherine Hoang <catherine.hoang@oracle.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 6.6 CANDIDATE 0/8] xfs backports for 6.6.y (from 6.9)
Date: Thu, 13 Jun 2024 20:57:01 -0700	[thread overview]
Message-ID: <20240614035701.GF6125@frogsfrogsfrogs> (raw)
In-Reply-To: <20240614014946.43237-1-catherine.hoang@oracle.com>

On Thu, Jun 13, 2024 at 06:49:38PM -0700, Catherine Hoang wrote:
> Hi all,
> 
> This series contains backports for 6.6 from the 6.9 release. Tested on
> 30 runs of kdevops with the following configurations:
> 
> 1. CRC
> 2. No CRC (512 and 4k block size)
> 3. Reflink (1K and 4k block size)
> 4. Reflink without rmapbt
> 5. External log device
> 
> Andrey Albershteyn (1):
>   xfs: allow cross-linking special files without project quota
> 
> Darrick J. Wong (2):
>   xfs: fix imprecise logic in xchk_btree_check_block_owner
>   xfs: fix scrub stats file permissions
> 
> Dave Chinner (4):
>   xfs: fix SEEK_HOLE/DATA for regions with active COW extents
>   xfs: shrink failure needs to hold AGI buffer
>   xfs: allow sunit mount option to repair bad primary sb stripe values
>   xfs: don't use current->journal_info
> 
> Long Li (1):
>   xfs: ensure submit buffers on LSN boundaries in error handlers

Looks good to me,
Acked-by: Darrick J. Wong <djwong@kernel.org>

--D

> 
>  fs/xfs/libxfs/xfs_ag.c   | 11 ++++++++++-
>  fs/xfs/libxfs/xfs_sb.c   | 40 +++++++++++++++++++++++++++++++---------
>  fs/xfs/libxfs/xfs_sb.h   |  5 +++--
>  fs/xfs/scrub/btree.c     |  7 ++++++-
>  fs/xfs/scrub/common.c    |  4 +---
>  fs/xfs/scrub/stats.c     |  4 ++--
>  fs/xfs/xfs_aops.c        |  7 -------
>  fs/xfs/xfs_icache.c      |  8 +++++---
>  fs/xfs/xfs_inode.c       | 15 +++++++++++++--
>  fs/xfs/xfs_iomap.c       |  4 ++--
>  fs/xfs/xfs_log_recover.c | 23 ++++++++++++++++++++---
>  fs/xfs/xfs_trans.h       |  9 +--------
>  12 files changed, 94 insertions(+), 43 deletions(-)
> 
> -- 
> 2.39.3
> 
> 

      parent reply	other threads:[~2024-06-14  3:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-14  1:49 [PATCH 6.6 CANDIDATE 0/8] xfs backports for 6.6.y (from 6.9) Catherine Hoang
2024-06-14  1:49 ` [PATCH 6.6 CANDIDATE 1/8] xfs: fix imprecise logic in xchk_btree_check_block_owner Catherine Hoang
2024-06-14  1:49 ` [PATCH 6.6 CANDIDATE 2/8] xfs: fix scrub stats file permissions Catherine Hoang
2024-06-14  1:49 ` [PATCH 6.6 CANDIDATE 3/8] xfs: fix SEEK_HOLE/DATA for regions with active COW extents Catherine Hoang
2024-06-14  1:49 ` [PATCH 6.6 CANDIDATE 4/8] xfs: shrink failure needs to hold AGI buffer Catherine Hoang
2024-06-14  1:49 ` [PATCH 6.6 CANDIDATE 5/8] xfs: ensure submit buffers on LSN boundaries in error handlers Catherine Hoang
2024-06-14  1:49 ` [PATCH 6.6 CANDIDATE 6/8] xfs: allow sunit mount option to repair bad primary sb stripe values Catherine Hoang
2024-06-14  1:49 ` [PATCH 6.6 CANDIDATE 7/8] xfs: don't use current->journal_info Catherine Hoang
2024-06-14  1:49 ` [PATCH 6.6 CANDIDATE 8/8] xfs: allow cross-linking special files without project quota Catherine Hoang
2024-06-14  3:57 ` 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=20240614035701.GF6125@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=catherine.hoang@oracle.com \
    --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