From: Amir Goldstein <amir73il@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Sasha Levin <sashal@kernel.org>,
"Darrick J . Wong" <djwong@kernel.org>,
Leah Rumancik <leah.rumancik@gmail.com>,
Chandan Babu R <chandan.babu@oracle.com>,
Luis Chamberlain <mcgrof@kernel.org>,
Adam Manzanares <a.manzanares@samsung.com>,
linux-xfs@vger.kernel.org, stable@vger.kernel.org
Subject: [PATCH 5.10 v4 0/5] xfs stable patches for 5.10.y (backports from v5.15.y)
Date: Mon, 27 Jun 2022 09:51:35 +0300 [thread overview]
Message-ID: <20220627065140.2798412-1-amir73il@gmail.com> (raw)
[resend with PATCH 5.10 prefix]
Hi Greg,
We started to experiment with the "xfs stable maintainers" concept that
Darrick has proposed.
My focus is on 5.10.y backports,
Leah's focus is on 5.15.y backports and
Chandan may pick up the 5.4.y backports.
This stable update is the first collaborated series for 5.10.y/5.15.y.
It started with a 5.15.y patch series from Leah [1] of patches that
specifically fix bugs prior to 5.10, to whom I already had tested
5.10 backport patches for.
Leah will be sending the ACKed 5.15.y series [2].
This 5.10.y series is a subset of the 5.15.y series that was
ACKed by xfs developers for 5.10.y.
All the patches in the 5.15.y series were backported to 5.10.
The ones that are not included in this 5.10.y update were more subtle
to backport, so the backports need more time for review and I will send
them in one of the following stable updates.
I would like to thank Darrick for reviewing the backport candidates.
I would like to thank Luis for his ongoing support of the kdevops [3]
test environment and Samsung for contributing the hardware to drive it.
Thanks,
Amir.
Changes since v3:
- PATCH 5.10 prefix
Changes since [v2]:
- CC stable
Changes since [v1]:
- Leave 5 out of 11
- Accked by Darrick
[1] https://lore.kernel.org/linux-xfs/20220616182749.1200971-1-leah.rumancik@gmail.com/
[2] https://lore.kernel.org/linux-xfs/20220623203641.1710377-1-leah.rumancik@gmail.com/
[3] https://github.com/linux-kdevops/kdevops
[v1] https://lore.kernel.org/linux-xfs/20220617100641.1653164-1-amir73il@gmail.com/
[v2] https://lore.kernel.org/linux-xfs/20220624063702.2380990-1-amir73il@gmail.com/
Brian Foster (1):
xfs: punch out data fork delalloc blocks on COW writeback failure
Darrick J. Wong (1):
xfs: remove all COW fork extents when remounting readonly
Dave Chinner (1):
xfs: check sb_meta_uuid for dabuf buffer recovery
Rustam Kovhaev (1):
xfs: use kmem_cache_free() for kmem_cache objects
Yang Xu (1):
xfs: Fix the free logic of state in xfs_attr_node_hasname
fs/xfs/libxfs/xfs_attr.c | 13 +++++--------
fs/xfs/xfs_aops.c | 15 ++++++++++++---
fs/xfs/xfs_buf_item_recover.c | 2 +-
fs/xfs/xfs_extfree_item.c | 6 +++---
fs/xfs/xfs_super.c | 14 +++++++++++---
5 files changed, 32 insertions(+), 18 deletions(-)
--
2.25.1
next reply other threads:[~2022-06-27 6:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 6:51 Amir Goldstein [this message]
2022-06-27 6:51 ` [PATCH 5.10 v4 1/5] xfs: use kmem_cache_free() for kmem_cache objects Amir Goldstein
2022-06-27 6:51 ` [PATCH 5.10 v4 2/5] xfs: punch out data fork delalloc blocks on COW writeback failure Amir Goldstein
2022-06-27 6:51 ` [PATCH 5.10 v4 3/5] xfs: Fix the free logic of state in xfs_attr_node_hasname Amir Goldstein
2022-06-27 6:51 ` [PATCH 5.10 v4 4/5] xfs: remove all COW fork extents when remounting readonly Amir Goldstein
2022-06-27 6:51 ` [PATCH 5.10 v4 5/5] xfs: check sb_meta_uuid for dabuf buffer recovery Amir Goldstein
2022-06-30 11:21 ` [PATCH 5.10 v4 0/5] xfs stable patches for 5.10.y (backports from v5.15.y) Greg Kroah-Hartman
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=20220627065140.2798412-1-amir73il@gmail.com \
--to=amir73il@gmail.com \
--cc=a.manzanares@samsung.com \
--cc=chandan.babu@oracle.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;
as well as URLs for NNTP newsgroup(s).