FS/XFS testing framework
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Leah Rumancik <leah.rumancik@gmail.com>,
	Chandan Babu R <chandan.babu@oracle.com>,
	linux-xfs@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH 5.10 CANDIDATE 0/4] xfs stable candidate patches for 5.10.y (from v5.15)
Date: Tue, 9 Aug 2022 09:28:20 -0700	[thread overview]
Message-ID: <YvKLJMq+thXk6wsW@magnolia> (raw)
In-Reply-To: <20220809111708.92768-1-amir73il@gmail.com>

On Tue, Aug 09, 2022 at 01:17:04PM +0200, Amir Goldstein wrote:
> Hi Darrick,
> 
> This is a small update of simple backports from v5.15 that shouldn't be
> too hard to review.
> 
> I rather take "remove support for disabling quota accounting" to 5.10.y
> even though it is not a proper bug fix, as a defensive measure and in
> order to match the expefctations of fstests from diabling quota.

I don't agree with making quotaoff a nop after 136 releases of the 5.10
series.  Turning off quota accounting on a running system might be
risky, but anyone who's using it in 5.10 most likely expects it to
continue working, infrequent warts and all.

> These backports survived the standard auto group soak for over 40 runs
> on the 5 test configs.
> 
> Please ACK.

Patches 2-4 are straightforward fixes, so:
Acked-by: Darrick J. Wong <djwong@kernel.org>

--D

> 
> Thanks,
> Amir.
> 
> Christoph Hellwig (1):
>   xfs: remove support for disabling quota accounting on a mounted file
>     system
> 
> Darrick J. Wong (1):
>   xfs: only set IOMAP_F_SHARED when providing a srcmap to a write
> 
> Dave Chinner (2):
>   mm: Add kvrealloc()
>   xfs: fix I_DONTCACHE
> 
>  fs/xfs/libxfs/xfs_trans_resv.c |  30 -----
>  fs/xfs/libxfs/xfs_trans_resv.h |   2 -
>  fs/xfs/xfs_dquot_item.c        | 134 ------------------
>  fs/xfs/xfs_dquot_item.h        |  17 ---
>  fs/xfs/xfs_icache.c            |   3 +-
>  fs/xfs/xfs_iomap.c             |   8 +-
>  fs/xfs/xfs_iops.c              |   2 +-
>  fs/xfs/xfs_log_recover.c       |   4 +-
>  fs/xfs/xfs_qm.c                |   2 +-
>  fs/xfs/xfs_qm.h                |   1 -
>  fs/xfs/xfs_qm_syscalls.c       | 240 ++-------------------------------
>  fs/xfs/xfs_trans_dquot.c       |  38 ------
>  include/linux/mm.h             |   2 +
>  mm/util.c                      |  15 +++
>  14 files changed, 40 insertions(+), 458 deletions(-)
> 
> -- 
> 2.25.1
> 

  parent reply	other threads:[~2022-08-09 16:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-09 11:17 [PATCH 5.10 CANDIDATE 0/4] xfs stable candidate patches for 5.10.y (from v5.15) Amir Goldstein
2022-08-09 11:17 ` [PATCH 5.10 CANDIDATE 1/4] xfs: remove support for disabling quota accounting on a mounted file system Amir Goldstein
2022-08-09 11:17 ` [PATCH 5.10 CANDIDATE 2/4] mm: Add kvrealloc() Amir Goldstein
2022-08-09 11:17 ` [PATCH 5.10 CANDIDATE 3/4] xfs: only set IOMAP_F_SHARED when providing a srcmap to a write Amir Goldstein
2022-08-09 11:17 ` [PATCH 5.10 CANDIDATE 4/4] xfs: fix I_DONTCACHE Amir Goldstein
2022-08-09 16:28 ` Darrick J. Wong [this message]
2022-08-09 16:29   ` [PATCH 5.10 CANDIDATE 0/4] xfs stable candidate patches for 5.10.y (from v5.15) Amir Goldstein

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=YvKLJMq+thXk6wsW@magnolia \
    --to=djwong@kernel.org \
    --cc=amir73il@gmail.com \
    --cc=chandan.babu@oracle.com \
    --cc=fstests@vger.kernel.org \
    --cc=leah.rumancik@gmail.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