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/7] xfs stable candidate patches for 5.10.y (from v5.17)
Date: Mon, 22 Aug 2022 09:52:56 -0700	[thread overview]
Message-ID: <YwO0aIOQ0HrZ78Sx@magnolia> (raw)
In-Reply-To: <20220822162802.1661512-1-amir73il@gmail.com>

On Mon, Aug 22, 2022 at 07:27:56PM +0300, Amir Goldstein wrote:
> Hi Darrick,
> 
> This is my collection of backports from v5.17.
> 
> Patch 1 is a small fix picked from Leah's part 3 series for 5.15.y [1].
> 
> Patch 2 is a small fix picked from Leah's part 4 series [2].
> I have some more fixes queued from part 4, but they are not from v5.17,
> so will be posted in another series for v5.18/v5.19 fixes.
> 
> Patches 3-6 are debt from the joint 5.10.y/5.15.y series [3].
> Per your request in the review of that series, I collected all
> the sync_fs patches and verified that they fix test xfs/546.
> 
> These patches have been spinning on kdevops for several days with
> no regressions observed.
> 
> Please ACK.

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

--D

> 
> Thanks,
> Amir.
> 
> [1] https://lore.kernel.org/linux-xfs/20220721213610.2794134-1-leah.rumancik@gmail.com/
> [2] https://lore.kernel.org/linux-xfs/20220819181431.4113819-1-leah.rumancik@gmail.com/
> [3] https://lore.kernel.org/linux-xfs/CAOQ4uxjrLUjStjDGOV2-0SK6ur07KZ8hAzb6JP+Dsm8=0iEbSA@mail.gmail.com/
> 
> Christoph Hellwig (1):
>   fs: remove __sync_filesystem
> 
> Dan Carpenter (1):
>   xfs: prevent a WARN_ONCE() in xfs_ioc_attr_list()
> 
> Darrick J. Wong (4):
>   xfs: reject crazy array sizes being fed to XFS_IOC_GETBMAP*
>   vfs: make sync_filesystem return errors from ->sync_fs
>   xfs: return errors in xfs_fs_sync_fs
>   xfs: only bother with sync_filesystem during readonly remount
> 
>  fs/sync.c          | 48 ++++++++++++++++++++++++----------------------
>  fs/xfs/xfs_ioctl.c |  4 ++--
>  fs/xfs/xfs_ioctl.h |  5 +++--
>  fs/xfs/xfs_super.c | 13 ++++++++++---
>  4 files changed, 40 insertions(+), 30 deletions(-)
> 
> -- 
> 2.25.1
> 

      parent reply	other threads:[~2022-08-22 16:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-22 16:27 [PATCH 5.10 CANDIDATE 0/7] xfs stable candidate patches for 5.10.y (from v5.17) Amir Goldstein
2022-08-22 16:27 ` [PATCH 5.10 CANDIDATE 1/6] xfs: prevent a WARN_ONCE() in xfs_ioc_attr_list() Amir Goldstein
2022-08-22 16:27 ` [PATCH 5.10 CANDIDATE 2/6] xfs: reject crazy array sizes being fed to XFS_IOC_GETBMAP* Amir Goldstein
2022-08-22 16:27 ` [PATCH 5.10 CANDIDATE 3/6] fs: remove __sync_filesystem Amir Goldstein
2022-08-22 16:28 ` [PATCH 5.10 CANDIDATE 4/6] vfs: make sync_filesystem return errors from ->sync_fs Amir Goldstein
2022-08-22 16:28 ` [PATCH 5.10 CANDIDATE 5/6] xfs: return errors in xfs_fs_sync_fs Amir Goldstein
2022-08-22 16:28 ` [PATCH 5.10 CANDIDATE 6/6] xfs: only bother with sync_filesystem during readonly remount Amir Goldstein
2022-08-22 16:52 ` 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=YwO0aIOQ0HrZ78Sx@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