From: Sasha Levin <sashal@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 11:34:23 -0500 [thread overview]
Message-ID: <Y+0Jj+biS10Qcm+q@sashalap> (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.
Queued up, thanks!
--
Thanks,
Sasha
prev parent reply other threads:[~2023-02-15 16:35 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 ` [PATCH 5.15 00/10] xfs backports for 5.15.y Darrick J. Wong
2023-02-15 16:34 ` Sasha Levin [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=Y+0Jj+biS10Qcm+q@sashalap \
--to=sashal@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