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>,
Dave Chinner <david@fromorbit.com>,
Christoph Hellwig <hch@lst.de>,
Christian Brauner <christian.brauner@ubuntu.com>,
linux-xfs@vger.kernel.org, fstests@vger.kernel.org
Subject: [PATCH 5.10 CANDIDATE 00/11] xfs stable candidate patches for 5.10.y (v5.15+)
Date: Fri, 17 Jun 2022 13:06:30 +0300 [thread overview]
Message-ID: <20220617100641.1653164-1-amir73il@gmail.com> (raw)
Hi all,
Previously posted candidates for 5.10.y followed chronological release
order.
Parts 1 and 2 of fixes from v5.10..v5.12 have already been applied to
v5.10.121.
Part 3 (from 5.13) has already been posted for review [3] on June 6,
but following feedback from Dave, I changed my focus to get the same
set of patches tested and reviewed for 5.10.y/5.15.y.
I do want to ask you guys to also find time to review part 3, because
we have a lot of catching up to do for 5.10.y, so we need to chew at
this debt at a reasonable rate.
This post has the matching set of patches for 5.10.y that goes with
Leah's first set of candidates for 5.15.y [1].
Most of the fixes are from v5.15..v5.17 except for patch 11 (v5.18-rc1).
All fix patches have been tagged with Fixes: by the author.
The patches have been soaking in kdepops since Sunday. They passed more
than 30 auto group runs with several different versions of xfsprogs.
The differences from Leah's 5.15.y:
- It is 11 patches and not 8 because of dependencies
- Patches 6,7 are non-fixes backported as dependency to patch 8 -
they have "backported .* for dependency" in their commit message
- Patches 3,4,11 needed changes to apply to 5.10.y - they have a
"backport" related comment in their commit message to explain what
changes were needed
- Patch 10 is a fix from v5.12 that is re-posted as a dependency for
patch 11
Darrick,
As the author patches 4,11 and sole reviewer of patch 3 (a.k.a
the non-cleanly applied patches), please take a closer look at those.
Patch 10 has been dropped from my part 2 candidates following concerns
raised by Dave and is now being re-posted following feedback from
Christian and Christoph [2].
If there are still concerns about patches 10 or 11, please raise a flag.
I can drop either of these patches before posting to stable if anyone
feels that they need more time to soak in master.
Thanks,
Amir.
[1] https://lore.kernel.org/linux-xfs/20220616182749.1200971-1-leah.rumancik@gmail.com/
[2] https://lore.kernel.org/linux-xfs/CAOQ4uxg4=m9zEFbDAKXx7CP7HYiMwtsYSJvq076oKpy-OhK1uw@mail.gmail.com/
[3] https://lore.kernel.org/linux-xfs/20220606160537.689915-1-amir73il@gmail.com/
Brian Foster (1):
xfs: punch out data fork delalloc blocks on COW writeback failure
Christoph Hellwig (2):
xfs: refactor xfs_file_fsync
xfs: fix up non-directory creation in SGID directories
Darrick J. Wong (4):
xfs: remove all COW fork extents when remounting readonly
xfs: prevent UAF in xfs_log_item_in_current_chkpt
xfs: only bother with sync_filesystem during readonly remount
xfs: use setattr_copy to set vfs inode attributes
Dave Chinner (2):
xfs: check sb_meta_uuid for dabuf buffer recovery
xfs: xfs_log_force_lsn isn't passed a LSN
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/libxfs/xfs_types.h | 1 +
fs/xfs/xfs_aops.c | 15 +++++--
fs/xfs/xfs_buf_item.c | 2 +-
fs/xfs/xfs_buf_item_recover.c | 2 +-
fs/xfs/xfs_dquot_item.c | 2 +-
fs/xfs/xfs_extfree_item.c | 6 +--
fs/xfs/xfs_file.c | 81 +++++++++++++++++++++--------------
fs/xfs/xfs_inode.c | 24 +++++------
fs/xfs/xfs_inode_item.c | 4 +-
fs/xfs/xfs_inode_item.h | 2 +-
fs/xfs/xfs_iops.c | 56 ++----------------------
fs/xfs/xfs_log.c | 27 ++++++------
fs/xfs/xfs_log.h | 4 +-
fs/xfs/xfs_log_cil.c | 32 ++++++--------
fs/xfs/xfs_log_priv.h | 15 +++----
fs/xfs/xfs_pnfs.c | 3 +-
fs/xfs/xfs_super.c | 21 ++++++---
fs/xfs/xfs_trans.c | 6 +--
fs/xfs/xfs_trans.h | 4 +-
20 files changed, 149 insertions(+), 171 deletions(-)
--
2.25.1
next reply other threads:[~2022-06-17 10:07 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 10:06 Amir Goldstein [this message]
2022-06-17 10:06 ` [PATCH 5.10 CANDIDATE 01/11] xfs: use kmem_cache_free() for kmem_cache objects Amir Goldstein
2022-06-17 10:06 ` [PATCH 5.10 CANDIDATE 02/11] xfs: punch out data fork delalloc blocks on COW writeback failure Amir Goldstein
2022-06-17 10:06 ` [PATCH 5.10 CANDIDATE 03/11] xfs: Fix the free logic of state in xfs_attr_node_hasname Amir Goldstein
2022-06-22 16:32 ` Darrick J. Wong
2022-06-22 18:46 ` Amir Goldstein
2022-06-22 21:50 ` Darrick J. Wong
2022-06-17 10:06 ` [PATCH 5.10 CANDIDATE 04/11] xfs: remove all COW fork extents when remounting readonly Amir Goldstein
2022-06-17 10:06 ` [PATCH 5.10 CANDIDATE 05/11] xfs: check sb_meta_uuid for dabuf buffer recovery Amir Goldstein
2022-06-17 10:06 ` [PATCH 5.10 CANDIDATE 06/11] xfs: refactor xfs_file_fsync Amir Goldstein
2022-06-17 10:06 ` [PATCH 5.10 CANDIDATE 07/11] xfs: xfs_log_force_lsn isn't passed a LSN Amir Goldstein
2022-06-22 16:45 ` Darrick J. Wong
2022-06-22 17:09 ` Amir Goldstein
2022-06-17 10:06 ` [PATCH 5.10 CANDIDATE 08/11] xfs: prevent UAF in xfs_log_item_in_current_chkpt Amir Goldstein
2022-06-17 10:06 ` [PATCH 5.10 CANDIDATE 09/11] xfs: only bother with sync_filesystem during readonly remount Amir Goldstein
2022-06-22 16:38 ` Darrick J. Wong
2022-06-22 16:54 ` Amir Goldstein
2022-06-22 23:42 ` Darrick J. Wong
2022-06-23 6:38 ` Amir Goldstein
2022-06-17 10:06 ` [PATCH 5.10 CANDIDATE 10/11] xfs: fix up non-directory creation in SGID directories Amir Goldstein
2022-06-17 10:06 ` [PATCH 5.10 CANDIDATE 11/11] xfs: use setattr_copy to set vfs inode attributes Amir Goldstein
2022-06-22 16:41 ` Darrick J. Wong
2022-06-22 18:36 ` Amir Goldstein
2022-06-22 22:17 ` Leah Rumancik
2022-06-23 4:22 ` Amir Goldstein
2022-06-22 23:45 ` [PATCH 5.10 CANDIDATE 00/11] xfs stable candidate patches for 5.10.y (v5.15+) Darrick J. Wong
2022-06-23 7:33 ` Amir Goldstein
2022-06-23 16:05 ` Darrick J. Wong
2022-07-24 8:36 ` Amir Goldstein
2022-07-26 2:10 ` Darrick J. Wong
2022-07-26 8:41 ` 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=20220617100641.1653164-1-amir73il@gmail.com \
--to=amir73il@gmail.com \
--cc=christian.brauner@ubuntu.com \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=hch@lst.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox