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 5.15 CANDIDATE 0/3] xfs stable candidate patches (part 5)
Date: Tue, 20 Sep 2022 17:36:54 -0700 [thread overview]
Message-ID: <YypcplVAkNX6o1gA@magnolia> (raw)
In-Reply-To: <20220920203750.1989625-1-leah.rumancik@gmail.com>
On Tue, Sep 20, 2022 at 01:37:47PM -0700, Leah Rumancik wrote:
> Hello,
>
> These patches correspond to the last two patches from the 5.10 series
> [1]. These patches were postponed for 5.10 until they were tested on
> 5.15. I have tested these on 5.15 (40 runs of the auto group x 4
> configs).
Looks good to me!
Acked-by: Darrick J. Wong <djwong@kernel.org>
--D
>
> Best,
> Leah
>
> [1] https://lore.kernel.org/linux-xfs/20220901054854.2449416-1-amir73il@gmail.com/
>
> Brian Foster (1):
> xfs: fix xfs_ifree() error handling to not leak perag ref
>
> Dave Chinner (2):
> xfs: reorder iunlink remove operation in xfs_ifree
> xfs: validate inode fork size against fork format
>
> fs/xfs/libxfs/xfs_inode_buf.c | 35 ++++++++++++++++++++++++++---------
> fs/xfs/xfs_inode.c | 22 ++++++++++++----------
> 2 files changed, 38 insertions(+), 19 deletions(-)
>
> --
> 2.37.3.968.ga6b4b080e4-goog
>
prev parent reply other threads:[~2022-09-21 0:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 20:37 [PATCH 5.15 CANDIDATE 0/3] xfs stable candidate patches (part 5) Leah Rumancik
2022-09-20 20:37 ` [PATCH 5.15 CANDIDATE 1/3] xfs: reorder iunlink remove operation in xfs_ifree Leah Rumancik
2022-09-20 20:37 ` [PATCH 5.15 CANDIDATE 2/3] xfs: fix xfs_ifree() error handling to not leak perag ref Leah Rumancik
2022-09-20 20:37 ` [PATCH 5.15 CANDIDATE 3/3] xfs: validate inode fork size against fork format Leah Rumancik
2022-09-21 0:36 ` 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=YypcplVAkNX6o1gA@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox