From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: "Darrick J. Wong" <djwong@kernel.org>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 1/4] xfs: do not check NEEDSREPAIR if ro,norecovery mount.
Date: Tue, 29 Apr 2025 08:49:45 -0400 [thread overview]
Message-ID: <20250429001646-bbac610a4e78b855@stable.kernel.org> (raw)
In-Reply-To: <174586545399.480536.11556523767440235148.stgit@frogsfrogsfrogs>
[ Sasha's backport helper bot ]
Hi,
✅ All tests passed successfully. No issues detected.
No action required from the submitter.
The upstream commit SHA1 provided is correct: 9e00163c31676c6b43d2334fdf5b406232f42dee
WARNING: Author mismatch between patch and upstream commit:
Backport author: "Darrick J. Wong"<djwong@kernel.org>
Commit author: Lukas Herbolt<lukas@herbolt.com>
Note: The patch differs from the upstream commit:
---
1: 9e00163c31676 < -: ------------- xfs: do not check NEEDSREPAIR if ro,norecovery mount.
-: ------------- > 1: ea061bad207e1 Linux 6.14.4
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-5.4.y | Success | Success |
next prev parent reply other threads:[~2025-04-29 12:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 18:39 [PATCHSET 6.12] xfs: backported fixes from upstream Darrick J. Wong
2025-04-28 18:39 ` [PATCH 1/4] xfs: do not check NEEDSREPAIR if ro,norecovery mount Darrick J. Wong
2025-04-29 12:49 ` Sasha Levin [this message]
2025-04-28 18:39 ` [PATCH 2/4] xfs: Do not allow norecovery mount with quotacheck Darrick J. Wong
2025-04-29 12:50 ` Sasha Levin
2025-04-28 18:39 ` [PATCH 3/4] xfs: rename xfs_iomap_swapfile_activate to xfs_vm_swap_activate Darrick J. Wong
2025-04-29 12:50 ` Sasha Levin
2025-04-28 18:40 ` [PATCH 4/4] xfs: flush inodegc before swapon Darrick J. Wong
2025-04-29 12:50 ` 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=20250429001646-bbac610a4e78b855@stable.kernel.org \
--to=sashal@kernel.org \
--cc=djwong@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