From: "Darrick J. Wong" <djwong@kernel.org>
To: Mahmoud Adam <mngyadam@amazon.com>
Cc: gregkh@linuxfoundation.org, stable@vger.kernel.org,
Amir Goldstein <amir73il@gmail.com>,
Leah Rumancik <lrumancik@google.com>,
Theodore Ts'o <tytso@mit.edu>
Subject: Re: [PATCH 6.1 0/6] backport xfs fix patches reported by xfs/179/270/557/606
Date: Wed, 3 Apr 2024 11:18:34 -0700 [thread overview]
Message-ID: <20240403181834.GA6414@frogsfrogsfrogs> (raw)
In-Reply-To: <20240403125949.33676-1-mngyadam@amazon.com>
On Wed, Apr 03, 2024 at 02:59:44PM +0200, Mahmoud Adam wrote:
> Hi,
>
> These patches fix and reported by xfstests tests xfs/179 xfs/270
> xfs/557 xfs/606, the patchset were tested to confirm they fix those
> tests. all are clean picks.
Hi! Thanks for the backports!
Normally I'd pass these on to the 6.1 XFS maintainer, but I'm not sure
who's actually taking care of that at the moment. To find out, I've
cc'd all the people who have either sent 6.1 backports or made noises
about doing so.
To the group: Who's the appropriate person to handle these?
Mahmoud: If the answer to the above is "???" or silence, would you be
willing to take on stable testing and maintenance?
Also FYI the normal practice (I think) is to cc linux-xfs, pick up some
acks, and then resend with the acks and cc'd to stable.
The six patches you sent along look ok to me, so
Acked-by: Darrick J. Wong <djwong@kernel.org>
--D
> thanks,
> MNAdam
next prev parent reply other threads:[~2024-04-03 18:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 12:59 [PATCH 6.1 0/6] backport xfs fix patches reported by xfs/179/270/557/606 Mahmoud Adam
2024-04-03 12:59 ` [PATCH 6.1 1/6] xfs: allow inode inactivation during a ro mount log recovery Mahmoud Adam
2024-04-03 12:59 ` [PATCH 6.1 2/6] xfs: fix log recovery when unknown rocompat bits are set Mahmoud Adam
2024-04-03 12:59 ` [PATCH 6.1 3/6] xfs: get root inode correctly at bulkstat Mahmoud Adam
2024-04-03 12:59 ` [PATCH 6.1 4/6] xfs: short circuit xfs_growfs_data_private() if delta is zero Mahmoud Adam
2024-04-03 12:59 ` [PATCH 6.1 5/6] xfs: hoist refcount record merge predicates Mahmoud Adam
2024-04-03 12:59 ` [PATCH 6.1 6/6] xfs: estimate post-merge refcounts correctly Mahmoud Adam
2024-04-03 18:18 ` Darrick J. Wong [this message]
2024-04-04 5:45 ` [PATCH 6.1 0/6] backport xfs fix patches reported by xfs/179/270/557/606 Amir Goldstein
2024-04-04 9:15 ` Mahmoud Adam
2024-04-05 9:27 ` Greg KH
2024-04-05 9:55 ` Amir Goldstein
2024-04-11 7:22 ` Greg KH
2024-04-11 17:27 ` Leah Rumancik
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=20240403181834.GA6414@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=amir73il@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=lrumancik@google.com \
--cc=mngyadam@amazon.com \
--cc=stable@vger.kernel.org \
--cc=tytso@mit.edu \
/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