From: Chandan Babu R <chandan.babu@oracle.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: sashal@kernel.org, mcgrof@kernel.org, linux-xfs@vger.kernel.org,
stable@vger.kernel.org, djwong@kernel.org, amir73il@gmail.com,
leah.rumancik@gmail.com
Subject: Re: [PATCH 5.4 00/17] xfs stable candidate patches for 5.4.y (from v5.11 & v5.12)
Date: Tue, 18 Apr 2023 18:09:32 +0530 [thread overview]
Message-ID: <87354xs4ni.fsf@debian-BULLSEYE-live-builder-AMD64> (raw)
In-Reply-To: <2023041814-conclude-herring-f2dd@gregkh>
On Tue, Apr 18, 2023 at 12:53:25 PM +0200, Greg KH wrote:
> On Tue, Apr 18, 2023 at 11:49:04AM +0200, Greg KH wrote:
>> On Wed, Apr 12, 2023 at 09:56:07AM +0530, Chandan Babu R wrote:
>> > Hi Greg,
>> >
>> > This 5.4.y backport series contains XFS fixes from v5.11 & v5.12. The
>> > patchset has been acked by Darrick.
>> >
>> > As a side note, where applicable, patches have been cherry picked from
>> > 5.10.y rather than from v5.11/v5.12.
>>
>> all now queued up, thanks.
>
> Wait, did you miss commit ada49d64fb35 ("xfs: fix forkoff miscalculation
> related to XFS_LITINO(mp)")?
Yes, unfortunately I missed that commit.
I always invoked my "find fixes" script as shown below,
# find-fixes-for-xfs-fixes.sh v5.11 v6.2 ~/junk/commits-fixes.log
The commits to be searched for "fixes for backported commits" spanned from the
kernel from which the fixes were backported to the latest upstream kernel. I
passed v5.11 as the argument since I was backporting patches from v5.11 and
v5.12.
However, e9e2eae89ddb ("xfs: only check the superblock version for dinode size
calculation") was from v5.7 and hence I missed ada49d64fb35.
# find-fixes-for-xfs-fixes.sh v5.4 v6.2 ~/junk/commits-fixes.log
ada49d64fb3538144192181db05de17e2ffc3551 e9e2eae89ddb
I will test the fix and send it out soon.
--
chandan
prev parent reply other threads:[~2023-04-18 13:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 4:26 [PATCH 5.4 00/17] xfs stable candidate patches for 5.4.y (from v5.11 & v5.12) Chandan Babu R
2023-04-12 4:26 ` [PATCH 5.4 01/17] xfs: show the proper user quota options Chandan Babu R
2023-04-12 4:26 ` [PATCH 5.4 02/17] xfs: merge the projid fields in struct xfs_icdinode Chandan Babu R
2023-04-12 4:26 ` [PATCH 5.4 03/17] xfs: ensure that the inode uid/gid match values match the icdinode ones Chandan Babu R
2023-04-12 4:26 ` [PATCH 5.4 04/17] xfs: remove the icdinode di_uid/di_gid members Chandan Babu R
2023-04-12 4:26 ` [PATCH 5.4 05/17] xfs: remove the kuid/kgid conversion wrappers Chandan Babu R
2023-04-12 4:26 ` [PATCH 5.4 06/17] xfs: add a new xfs_sb_version_has_v3inode helper Chandan Babu R
2023-04-12 4:26 ` [PATCH 5.4 07/17] xfs: only check the superblock version for dinode size calculation Chandan Babu R
2023-04-12 4:26 ` [PATCH 5.4 08/17] xfs: simplify di_flags2 inheritance in xfs_ialloc Chandan Babu R
2023-04-12 4:26 ` [PATCH 5.4 09/17] xfs: simplify a check in xfs_ioctl_setattr_check_cowextsize Chandan Babu R
2023-04-12 4:29 ` kernel test robot
2023-04-12 4:36 ` Chandan Babu R
2023-04-12 4:47 ` Philip Li
2023-04-12 4:50 ` Chandan Babu R
2023-04-12 5:08 ` [PATCH 5.4 V2] " Chandan Babu R
2023-04-12 4:26 ` [PATCH 5.4 10/17] xfs: remove the di_version field from struct icdinode Chandan Babu R
2023-04-12 4:26 ` [PATCH 5.4 11/17] xfs: fix up non-directory creation in SGID directories Chandan Babu R
2023-04-12 4:26 ` [PATCH 5.4 12/17] xfs: set inode size after creating symlink Chandan Babu R
2023-04-12 4:26 ` [PATCH 5.4 13/17] xfs: report corruption only as a regular error Chandan Babu R
2023-04-12 4:26 ` [PATCH 5.4 14/17] xfs: shut down the filesystem if we screw up quota reservation Chandan Babu R
2023-04-12 4:26 ` [PATCH 5.4 15/17] xfs: consider shutdown in bmapbt cursor delete assert Chandan Babu R
2023-04-12 4:26 ` [PATCH 5.4 16/17] xfs: don't reuse busy extents on extent trim Chandan Babu R
2023-04-12 4:26 ` [PATCH 5.4 17/17] xfs: force log and push AIL to clear pinned inodes when aborting mount Chandan Babu R
2023-04-18 9:49 ` [PATCH 5.4 00/17] xfs stable candidate patches for 5.4.y (from v5.11 & v5.12) Greg KH
2023-04-18 10:53 ` Greg KH
2023-04-18 12:39 ` Chandan Babu R [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=87354xs4ni.fsf@debian-BULLSEYE-live-builder-AMD64 \
--to=chandan.babu@oracle.com \
--cc=amir73il@gmail.com \
--cc=djwong@kernel.org \
--cc=gregkh@linuxfoundation.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