From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Sasha Levin <sashal@kernel.org>,
"Darrick J . Wong" <djwong@kernel.org>,
Leah Rumancik <leah.rumancik@gmail.com>,
Chandan Babu R <chandan.babu@oracle.com>,
Luis Chamberlain <mcgrof@kernel.org>,
Adam Manzanares <a.manzanares@samsung.com>,
linux-xfs@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 5.10 v2 0/9] xfs stable patches for 5.10.y (from v5.13+)
Date: Mon, 1 Aug 2022 10:41:52 +0200 [thread overview]
Message-ID: <YueR0E274KDHEO3T@kroah.com> (raw)
In-Reply-To: <20220729161609.4071252-1-amir73il@gmail.com>
On Fri, Jul 29, 2022 at 06:16:00PM +0200, Amir Goldstein wrote:
> Hi Greg,
>
> This backport series contains mostly fixes from v5.14 release along
> with one fix deferred from the first joint 5.10/5.15 series [1].
>
> The upstream commit f8d92a66e810 ("xfs: prevent UAF in
> xfs_log_item_in_current_chkpt") was already applied to 5.15.y, but its
> 5.10.y backport was more involved (required two non trivial dependency
> patches), so it needed more time for review and testing.
>
> Per Darrick's recommendation, on top of the usual regression tests,
> I also ran the "recoveryloop" tests group for an extended period of
> time to test for rare regressions.
>
> Some recoveryloop tests were failing at rates less frequent than 1/100,
> but no change in failure rate was observed between baseline (v5.10.131)
> and the backport branch.
>
> There was one exceptional test, xfs/455, that was reporting data
> corruptions after crash at very low rate - less frequent than 1/1000
> on both baseline and backport branch.
>
> It is hard to draw solid conclusions with such rare failures, but the
> test was run >10,000 times on baseline and >20,000 times on backport
> branch, so as far as our test coverage can attest, these backports are
> not introducing any obvious xfs regressions to 5.10.y.
Now queued up, thanks!
greg k-h
prev parent reply other threads:[~2022-08-01 8:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 16:16 [PATCH 5.10 v2 0/9] xfs stable patches for 5.10.y (from v5.13+) Amir Goldstein
2022-07-29 16:16 ` [PATCH 5.10 v2 1/9] xfs: refactor xfs_file_fsync Amir Goldstein
2022-07-29 16:16 ` [PATCH 5.10 v2 2/9] xfs: xfs_log_force_lsn isn't passed a LSN Amir Goldstein
2022-07-29 16:16 ` [PATCH 5.10 v2 3/9] xfs: prevent UAF in xfs_log_item_in_current_chkpt Amir Goldstein
2022-07-29 16:16 ` [PATCH 5.10 v2 4/9] xfs: fix log intent recovery ENOSPC shutdowns when inactivating inodes Amir Goldstein
2022-07-29 16:16 ` [PATCH 5.10 v2 5/9] xfs: force the log offline when log intent item recovery fails Amir Goldstein
2022-07-29 16:16 ` [PATCH 5.10 v2 6/9] xfs: hold buffer across unpin and potential shutdown processing Amir Goldstein
2022-07-29 16:16 ` [PATCH 5.10 v2 7/9] xfs: remove dead stale buf unpin handling code Amir Goldstein
2022-07-29 16:16 ` [PATCH 5.10 v2 8/9] xfs: logging the on disk inode LSN can make it go backwards Amir Goldstein
2022-07-29 16:16 ` [PATCH 5.10 v2 9/9] xfs: Enforce attr3 buffer recovery order Amir Goldstein
2022-08-01 8:41 ` Greg Kroah-Hartman [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=YueR0E274KDHEO3T@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=a.manzanares@samsung.com \
--cc=amir73il@gmail.com \
--cc=chandan.babu@oracle.com \
--cc=djwong@kernel.org \
--cc=leah.rumancik@gmail.com \
--cc=linux-xfs@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=sashal@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;
as well as URLs for NNTP newsgroup(s).