From: "Darrick J. Wong" <djwong@kernel.org>
To: Leah Rumancik <leah.rumancik@gmail.com>
Cc: linux-xfs@vger.kernel.org, amir73il@gmail.com
Subject: Re: [PATCH CANDIDATE 5.15 0/9] xfs stable candidate patches for 5.15.y (part 4)
Date: Wed, 17 Aug 2022 17:21:57 -0700 [thread overview]
Message-ID: <Yv2GJUk+/6JPbmFu@magnolia> (raw)
In-Reply-To: <20220817005610.3170067-1-leah.rumancik@gmail.com>
On Tue, Aug 16, 2022 at 05:56:01PM -0700, Leah Rumancik wrote:
> Hello,
>
> No regressions were found for this set via the usual testing.
>
> Additional targeted testing:
>
> generic/691 for bc37e4fb5cac
> generic/681 for 871b9316e7a7
> generic/682 for 41667260bc84
> Ensured these regression tests failed before but not after backports
>
> xfs/170 for f650df7171b88
> Was not able to reproduce failure before or after on my setup
Looks good to me,
Acked-by: Darrick J. Wong <djwong@kernel.org>
--D
>
> - Leah
>
> Brian Foster (2):
> xfs: flush inodegc workqueue tasks before cancel
> xfs: fix soft lockup via spinning in filestream ag selection loop
>
> Darrick J. Wong (6):
> xfs: reserve quota for dir expansion when linking/unlinking files
> xfs: reserve quota for target dir expansion when renaming files
> xfs: remove infinite loop when reserving free block pool
> xfs: always succeed at setting the reserve pool size
> xfs: fix overfilling of reserve pool
> xfs: reject crazy array sizes being fed to XFS_IOC_GETBMAP*
>
> Eric Sandeen (1):
> xfs: revert "xfs: actually bump warning counts when we send warnings"
>
> fs/xfs/xfs_filestream.c | 7 ++--
> fs/xfs/xfs_fsops.c | 50 ++++++++++-------------
> fs/xfs/xfs_icache.c | 22 ++--------
> fs/xfs/xfs_inode.c | 79 ++++++++++++++++++++++--------------
> fs/xfs/xfs_ioctl.c | 2 +-
> fs/xfs/xfs_trans.c | 86 ++++++++++++++++++++++++++++++++++++++++
> fs/xfs/xfs_trans.h | 3 ++
> fs/xfs/xfs_trans_dquot.c | 1 -
> 8 files changed, 167 insertions(+), 83 deletions(-)
>
> --
> 2.37.1.595.g718a3a8f04-goog
>
prev parent reply other threads:[~2022-08-18 0:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 0:56 [PATCH CANDIDATE 5.15 0/9] xfs stable candidate patches for 5.15.y (part 4) Leah Rumancik
2022-08-17 0:56 ` [PATCH CANDIDATE 5.15 1/9] xfs: flush inodegc workqueue tasks before cancel Leah Rumancik
2022-08-17 0:56 ` [PATCH CANDIDATE 5.15 2/9] xfs: reserve quota for dir expansion when linking/unlinking files Leah Rumancik
2022-08-17 0:56 ` [PATCH CANDIDATE 5.15 3/9] xfs: reserve quota for target dir expansion when renaming files Leah Rumancik
2022-08-17 0:56 ` [PATCH CANDIDATE 5.15 4/9] xfs: remove infinite loop when reserving free block pool Leah Rumancik
2022-08-17 0:56 ` [PATCH CANDIDATE 5.15 5/9] xfs: always succeed at setting the reserve pool size Leah Rumancik
2022-08-17 0:56 ` [PATCH CANDIDATE 5.15 6/9] xfs: fix overfilling of reserve pool Leah Rumancik
2022-08-17 0:56 ` [PATCH CANDIDATE 5.15 7/9] xfs: fix soft lockup via spinning in filestream ag selection loop Leah Rumancik
2022-08-17 0:56 ` [PATCH CANDIDATE 5.15 8/9] xfs: revert "xfs: actually bump warning counts when we send warnings" Leah Rumancik
2022-08-17 0:56 ` [PATCH CANDIDATE 5.15 9/9] xfs: reject crazy array sizes being fed to XFS_IOC_GETBMAP* Leah Rumancik
2022-08-18 0:21 ` 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=Yv2GJUk+/6JPbmFu@magnolia \
--to=djwong@kernel.org \
--cc=amir73il@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.