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/5] xfs: sb_spino_align is not verified
Date: Wed, 18 Dec 2024 16:43:27 -0500 [thread overview]
Message-ID: <20241218163854-e24d7355695cb5bd@stable.kernel.org> (raw)
In-Reply-To: <173455093514.305755.18242328636177192354.stgit@frogsfrogsfrogs>
[ Sasha's backport helper bot ]
Hi,
The upstream commit SHA1 provided is correct: 59e43f5479cce106d71c0b91a297c7ad1913176c
WARNING: Author mismatch between patch and upstream commit:
Backport author: "Darrick J. Wong" <djwong@kernel.org>
Commit author: Dave Chinner <dchinner@redhat.com>
Status in newer kernel trees:
6.12.y | Not found
Note: The patch differs from the upstream commit:
---
1: 59e43f5479cc ! 1: 273f71b3b9d4 xfs: sb_spino_align is not verified
@@ Metadata
## Commit message ##
xfs: sb_spino_align is not verified
+ commit 59e43f5479cce106d71c0b91a297c7ad1913176c upstream.
+
It's just read in from the superblock and used without doing any
validity checks at all on the value.
@@ Commit message
Signed-off-by: Dave Chinner <dchinner@redhat.com>
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
Signed-off-by: Carlos Maiolino <cem@kernel.org>
+ [djwong: actually tag for 6.12 because upstream maintainer ignored cc-stable tag]
+ Link: https://lore.kernel.org/linux-xfs/20241024165544.GI21853@frogsfrogsfrogs/
+ Signed-off-by: "Darrick J. Wong" <djwong@kernel.org>
## fs/xfs/libxfs/xfs_sb.c ##
@@ fs/xfs/libxfs/xfs_sb.c: xfs_validate_sb_common(
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.12.y | Success | Success |
| stable/linux-6.6.y | Success | Success |
| stable/linux-6.1.y | Success | Success |
| stable/linux-5.15.y | Success | Success |
| stable/linux-5.10.y | Failed | N/A |
| stable/linux-5.4.y | Failed | N/A |
next prev parent reply other threads:[~2024-12-18 21:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-18 19:50 [PATCHSET 6.12] xfs: bug fixes for 6.12.y LTS Darrick J. Wong
2024-12-18 19:50 ` [PATCH 1/5] xfs: sb_spino_align is not verified Darrick J. Wong
2024-12-18 21:43 ` Sasha Levin [this message]
2024-12-18 19:50 ` [PATCH 2/5] xfs: fix sparse inode limits on runt AG Darrick J. Wong
2024-12-18 19:50 ` [PATCH 3/5] xfs: fix off-by-one error in fsmap's end_daddr usage Darrick J. Wong
2024-12-18 19:51 ` [PATCH 4/5] xfs: fix sb_spino_align checks for large fsblock sizes Darrick J. Wong
2024-12-18 19:51 ` [PATCH 5/5] xfs: fix zero byte checking in the superblock scrubber Darrick J. Wong
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=20241218163854-e24d7355695cb5bd@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.