From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Catherine Hoang <catherine.hoang@oracle.com>,
Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.6 07/17] xfs: Fix xfs_prepare_shift() range for RT
Date: Wed, 18 Dec 2024 16:01:15 -0500 [thread overview]
Message-ID: <20241218153217-48a33690faf4edca@stable.kernel.org> (raw)
In-Reply-To: <20241218191725.63098-8-catherine.hoang@oracle.com>
[ Sasha's backport helper bot ]
Hi,
The upstream commit SHA1 provided is correct: f23660f059470ec7043748da7641e84183c23bc8
WARNING: Author mismatch between patch and upstream commit:
Backport author: Catherine Hoang <catherine.hoang@oracle.com>
Commit author: John Garry <john.g.garry@oracle.com>
Status in newer kernel trees:
6.12.y | Present (exact SHA1)
6.6.y | Not found
Note: The patch differs from the upstream commit:
---
1: f23660f05947 ! 1: 7aa03646d5cc xfs: Fix xfs_prepare_shift() range for RT
@@ Metadata
## Commit message ##
xfs: Fix xfs_prepare_shift() range for RT
+ commit f23660f059470ec7043748da7641e84183c23bc8 upstream.
+
The RT extent range must be considered in the xfs_flush_unmap_range() call
to stabilize the boundary.
@@ Commit message
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
Signed-off-by: John Garry <john.g.garry@oracle.com>
Signed-off-by: Chandan Babu R <chandanbabu@kernel.org>
+ Signed-off-by: Catherine Hoang <catherine.hoang@oracle.com>
+ Acked-by: Darrick J. Wong <djwong@kernel.org>
## fs/xfs/xfs_bmap_util.c ##
@@ fs/xfs/xfs_bmap_util.c: xfs_prepare_shift(
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.6.y | Success | Success |
next prev parent reply other threads:[~2024-12-18 21:01 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-18 19:17 [PATCH 6.6 00/17] xfs backports for 6.6.y (from 6.11) Catherine Hoang
2024-12-18 19:17 ` [PATCH 6.6 01/17] xfs: fix the contact address for the sysfs ABI documentation Catherine Hoang
2024-12-18 21:01 ` Sasha Levin
2024-12-18 19:17 ` [PATCH 6.6 02/17] xfs: verify buffer, inode, and dquot items every tx commit Catherine Hoang
2024-12-18 21:01 ` Sasha Levin
2024-12-18 19:17 ` [PATCH 6.6 03/17] xfs: use consistent uid/gid when grabbing dquots for inodes Catherine Hoang
2024-12-18 21:01 ` Sasha Levin
2024-12-18 19:17 ` [PATCH 6.6 04/17] xfs: declare xfs_file.c symbols in xfs_file.h Catherine Hoang
2024-12-18 21:01 ` Sasha Levin
2024-12-18 19:17 ` [PATCH 6.6 05/17] xfs: create a new helper to return a file's allocation unit Catherine Hoang
2024-12-18 21:01 ` Sasha Levin
2024-12-18 19:17 ` [PATCH 6.6 06/17] xfs: Fix xfs_flush_unmap_range() range for RT Catherine Hoang
2024-12-18 21:00 ` Sasha Levin
2024-12-18 19:17 ` [PATCH 6.6 07/17] xfs: Fix xfs_prepare_shift() " Catherine Hoang
2024-12-18 21:01 ` Sasha Levin [this message]
2024-12-18 19:17 ` [PATCH 6.6 08/17] xfs: don't walk off the end of a directory data block Catherine Hoang
2024-12-18 21:01 ` Sasha Levin
2024-12-18 19:17 ` [PATCH 6.6 09/17] xfs: convert comma to semicolon Catherine Hoang
2024-12-18 21:01 ` Sasha Levin
2024-12-18 19:17 ` [PATCH 6.6 10/17] xfs: fix file_path handling in tracepoints Catherine Hoang
2024-12-18 21:01 ` Sasha Levin
2024-12-18 19:17 ` [PATCH 6.6 11/17] xfs: remove unused parameter in macro XFS_DQUOT_LOGRES Catherine Hoang
2024-12-18 21:01 ` Sasha Levin
2024-12-18 19:17 ` [PATCH 6.6 12/17] xfs: attr forks require attr, not attr2 Catherine Hoang
2024-12-18 21:01 ` Sasha Levin
2024-12-18 22:13 ` Sasha Levin
2024-12-18 19:17 ` [PATCH 6.6 13/17] xfs: conditionally allow FS_XFLAG_REALTIME changes if S_DAX is set Catherine Hoang
2024-12-18 19:17 ` [PATCH 6.6 14/17] xfs: Fix the owner setting issue for rmap query in xfs fsmap Catherine Hoang
2024-12-18 19:17 ` [PATCH 6.6 15/17] xfs: use XFS_BUF_DADDR_NULL for daddrs in getfsmap code Catherine Hoang
2024-12-18 19:17 ` [PATCH 6.6 16/17] xfs: take m_growlock when running growfsrt Catherine Hoang
2024-12-18 19:17 ` [PATCH 6.6 17/17] xfs: reset rootdir extent size hint after growfsrt Catherine Hoang
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=20241218153217-48a33690faf4edca@stable.kernel.org \
--to=sashal@kernel.org \
--cc=catherine.hoang@oracle.com \
--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.