From: Amir Goldstein <amir73il@gmail.com>
To: "Darrick J . Wong" <djwong@kernel.org>
Cc: Leah Rumancik <leah.rumancik@gmail.com>,
Luis Chamberlain <mcgrof@kernel.org>,
linux-xfs@vger.kernel.org, fstests@vger.kernel.org
Subject: [5.10 CANDIDATE v2 0/5] xfs stable candidate patches for 5.10.y (v5.15+)
Date: Fri, 24 Jun 2022 09:36:57 +0300 [thread overview]
Message-ID: <20220624063702.2380990-1-amir73il@gmail.com> (raw)
Hi all,
This is the subset of patches from Leah's 5.15.y series [1] that was
tested and ACKed for 5.10.y.
The rest of the patches were more subtle to backport, so they need more
time for review.
One patch in v1 also needed missing vfs patches (syncfs error) so those
need to be tested in 5.10 as well before being posted again.
I will send these 5 patches to stable in a few days if there are no
further comments.
Thanks,
Amir.
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/
[v1] https://lore.kernel.org/linux-xfs/20220617100641.1653164-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-24 6:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 6:36 Amir Goldstein [this message]
2022-06-24 6:36 ` [5.10 CANDIDATE v2 1/5] xfs: use kmem_cache_free() for kmem_cache objects Amir Goldstein
2022-06-24 6:36 ` [5.10 CANDIDATE v2 2/5] xfs: punch out data fork delalloc blocks on COW writeback failure Amir Goldstein
2022-06-24 6:37 ` [5.10 CANDIDATE v2 3/5] xfs: Fix the free logic of state in xfs_attr_node_hasname Amir Goldstein
2022-06-24 6:37 ` [5.10 CANDIDATE v2 4/5] xfs: remove all COW fork extents when remounting readonly Amir Goldstein
2022-06-24 6:37 ` [5.10 CANDIDATE v2 5/5] xfs: check sb_meta_uuid for dabuf buffer recovery Amir Goldstein
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=20220624063702.2380990-1-amir73il@gmail.com \
--to=amir73il@gmail.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=leah.rumancik@gmail.com \
--cc=linux-xfs@vger.kernel.org \
--cc=mcgrof@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.