From: "Darrick J. Wong" <djwong@kernel.org>
To: Leah Rumancik <leah.rumancik@gmail.com>
Cc: stable@vger.kernel.org, linux-xfs@vger.kernel.org,
amir73il@gmail.com, chandan.babu@oracle.com
Subject: Re: [PATCH 5.15 00/10] xfs backports for 5.15.y
Date: Wed, 15 Feb 2023 08:24:52 -0800 [thread overview]
Message-ID: <Y+0HVLgoXMWCAtYX@magnolia> (raw)
In-Reply-To: <20230214212534.1420323-1-leah.rumancik@gmail.com>
On Tue, Feb 14, 2023 at 01:25:24PM -0800, Leah Rumancik wrote:
> Hello,
>
> Here is the next batch of backports for 5.15.y. These patches have
> already been ACK'd on the xfs mailing list. Testing included
> 25 runs of auto group on 12 xfs configs. No regressions were seen.
> I checked xfs/538 was run without issue as this test was mentioned
> in 56486f307100. Also, from 86d40f1e49e9, I ran ran xfs/117 with
> XFS compiled as a module and TEST_FS_MODULE_REOLOAD set, but I was
> unable to reproduce the issue.
>
> Below I've outlined which series the backports came from:
>
> series "xfs: intent whiteouts" (1):
> [01/10] cb512c921639613ce03f87e62c5e93ed9fe8c84d
> xfs: zero inode fork buffer at allocation
> [02/10] c230a4a85bcdbfc1a7415deec6caf04e8fca1301
> xfs: fix potential log item leak
>
> series "xfs: fix random format verification issues" (2):
> [1/4] dc04db2aa7c9307e740d6d0e173085301c173b1a
> xfs: detect self referencing btree sibling pointers
> [2/4] 1eb70f54c445fcbb25817841e774adb3d912f3e8 -> already in 5.15.y
> xfs: validate inode fork size against fork format
> [3/4] dd0d2f9755191690541b09e6385d0f8cd8bc9d8f
> xfs: set XFS_FEAT_NLINK correctly
> [4/4] f0f5f658065a5af09126ec892e4c383540a1c77f
> xfs: validate v5 feature fields
>
> series "xfs: small fixes for 5.19 cycle" (3):
> [1/3] 5672225e8f2a872a22b0cecedba7a6644af1fb84
> xfs: avoid unnecessary runtime sibling pointer endian conversions
> [2/3] 5b55cbc2d72632e874e50d2e36bce608e55aaaea
> fs: don't assert fail on perag references on teardown
> [2/3] 56486f307100e8fc66efa2ebd8a71941fa10bf6f
> xfs: assert in xfs_btree_del_cursor should take into account error
>
> series "xfs: random fixes for 5.19" (4):
> [1/2] 86d40f1e49e9a909d25c35ba01bea80dbcd758cb
> xfs: purge dquots after inode walk fails during quotacheck
> [2/2] a54f78def73d847cb060b18c4e4a3d1d26c9ca6d
> xfs: don't leak btree cursor when insrec fails after a split
Looks good!
Acked-by: Darrick J. Wong <djwong@kernel.org>
--D
>
> (1) https://lore.kernel.org/all/20220503221728.185449-1-david@fromorbit.com/
> (2) https://lore.kernel.org/all/20220502082018.1076561-1-david@fromorbit.com/
> (3) https://lore.kernel.org/all/20220524022158.1849458-1-david@fromorbit.com/
> (4) https://lore.kernel.org/all/165337056527.993079.1232300816023906959.stgit@magnolia/
>
> - Leah
>
> Darrick J. Wong (2):
> xfs: purge dquots after inode walk fails during quotacheck
> xfs: don't leak btree cursor when insrec fails after a split
>
> Dave Chinner (8):
> xfs: zero inode fork buffer at allocation
> xfs: fix potential log item leak
> xfs: detect self referencing btree sibling pointers
> xfs: set XFS_FEAT_NLINK correctly
> xfs: validate v5 feature fields
> xfs: avoid unnecessary runtime sibling pointer endian conversions
> xfs: don't assert fail on perag references on teardown
> xfs: assert in xfs_btree_del_cursor should take into account error
>
> fs/xfs/libxfs/xfs_ag.c | 3 +-
> fs/xfs/libxfs/xfs_btree.c | 175 +++++++++++++++++++++++++--------
> fs/xfs/libxfs/xfs_inode_fork.c | 12 ++-
> fs/xfs/libxfs/xfs_sb.c | 70 +++++++++++--
> fs/xfs/xfs_bmap_item.c | 2 +
> fs/xfs/xfs_icreate_item.c | 1 +
> fs/xfs/xfs_qm.c | 9 +-
> fs/xfs/xfs_refcount_item.c | 2 +
> fs/xfs/xfs_rmap_item.c | 2 +
> 9 files changed, 221 insertions(+), 55 deletions(-)
>
> --
> 2.39.1.581.gbfd45094c4-goog
>
next prev parent reply other threads:[~2023-02-15 16:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 21:25 [PATCH 5.15 00/10] xfs backports for 5.15.y Leah Rumancik
2023-02-14 21:25 ` [PATCH 5.15 01/10] xfs: zero inode fork buffer at allocation Leah Rumancik
2023-02-14 21:25 ` [PATCH 5.15 02/10] xfs: fix potential log item leak Leah Rumancik
2023-02-14 21:25 ` [PATCH 5.15 03/10] xfs: detect self referencing btree sibling pointers Leah Rumancik
2023-02-14 21:25 ` [PATCH 5.15 04/10] xfs: set XFS_FEAT_NLINK correctly Leah Rumancik
2023-02-14 21:25 ` [PATCH 5.15 05/10] xfs: validate v5 feature fields Leah Rumancik
2023-02-14 21:25 ` [PATCH 5.15 06/10] xfs: avoid unnecessary runtime sibling pointer endian conversions Leah Rumancik
2023-02-14 21:25 ` [PATCH 5.15 07/10] xfs: don't assert fail on perag references on teardown Leah Rumancik
2023-02-14 21:25 ` [PATCH 5.15 08/10] xfs: assert in xfs_btree_del_cursor should take into account error Leah Rumancik
2023-02-14 21:25 ` [PATCH 5.15 09/10] xfs: purge dquots after inode walk fails during quotacheck Leah Rumancik
2023-02-14 21:25 ` [PATCH 5.15 10/10] xfs: don't leak btree cursor when insrec fails after a split Leah Rumancik
2023-02-15 16:24 ` Darrick J. Wong [this message]
2023-02-15 16:34 ` [PATCH 5.15 00/10] xfs backports for 5.15.y Sasha Levin
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=Y+0HVLgoXMWCAtYX@magnolia \
--to=djwong@kernel.org \
--cc=amir73il@gmail.com \
--cc=chandan.babu@oracle.com \
--cc=leah.rumancik@gmail.com \
--cc=linux-xfs@vger.kernel.org \
--cc=stable@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