From: Long Li <leo.lilong@huaweicloud.com>
To: Chandan Babu R <chandanbabu@kernel.org>
Cc: linux-xfs@vger.kernel.org, yi.zhang@huawei.com,
houtao1@huawei.com, yangerkun@huawei.com, djwong@kernel.org,
david@fromorbit.com
Subject: Re: [PATCH v3 0/3] xfs: fix two problem when recovery intents fails
Date: Tue, 7 Nov 2023 21:36:07 +0800 [thread overview]
Message-ID: <20231107133607.GA560725@ceph-admin> (raw)
In-Reply-To: <20230731124619.3925403-1-leo.lilong@huawei.com>
On Mon, Jul 31, 2023 at 08:46:16PM +0800, Long Li wrote:
> This patch set fix two problem when recovery intents fails.
>
> Patches 1-2 fix the possible problem that intent items not released.
> When recovery intents, new intents items may be created during recovery
> intents. if recovery fails, new intents items may be left in AIL or
> leaks.
Hi Chandan,
In this patchset, patches 1-2 [1][2] have already been reviewed by Darrick,
and are not related to patch 3, is it possible to merge patches 1-2 in first??
Patch 3 seems still has a lot of work to do.
[1] https://patchwork.kernel.org/project/xfs/patch/20230715063647.2094989-2-leo.lilong@huawei.com/
[2] https://patchwork.kernel.org/project/xfs/patch/20230715063647.2094989-3-leo.lilong@huawei.com/
Thanks,
Long Li
>
> Patch 3 fix a uaf problem, when recovery intents fails, intent items
> may be freed before done item commited.
>
> v3:
> - Modified as suggested by Dave, solves the UAF problem by correctly
> handling the reference counting of intents in patch 3
>
> v2:
> - change xfs_defer_pending_abort to static in patch 1
> - rewrite commit message in patch 2-3
> - rename xfs_defer_ops_capture_free to xfs_defer_ops_capture_abort, and
> add xfs_defer_pending_abort to the start of xfs_defer_ops_capture_abort
>
>
> Long Li (3):
> xfs: factor out xfs_defer_pending_abort
> xfs: abort intent items when recovery intents fail
> xfs: fix intent item uaf when recover intents fail
>
> fs/xfs/libxfs/xfs_defer.c | 28 ++++++++++++++++++----------
> fs/xfs/libxfs/xfs_defer.h | 2 +-
> fs/xfs/xfs_attr_item.c | 1 +
> fs/xfs/xfs_bmap_item.c | 1 +
> fs/xfs/xfs_extfree_item.c | 1 +
> fs/xfs/xfs_log_recover.c | 2 +-
> fs/xfs/xfs_refcount_item.c | 1 +
> fs/xfs/xfs_rmap_item.c | 1 +
> 8 files changed, 25 insertions(+), 12 deletions(-)
>
> --
> 2.31.1
>
next prev parent reply other threads:[~2023-11-07 13:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 12:46 [PATCH v3 0/3] xfs: fix two problem when recovery intents fails Long Li
2023-07-31 12:46 ` [PATCH v3 1/3] xfs: factor out xfs_defer_pending_abort Long Li
2023-07-31 12:46 ` [PATCH v3 2/3] xfs: abort intent items when recovery intents fail Long Li
2023-07-31 12:46 ` [PATCH v3 3/3] xfs: fix intent item uaf when recover " Long Li
2023-08-24 4:34 ` Darrick J. Wong
2023-10-14 9:13 ` Long Li
2023-11-21 1:26 ` Darrick J. Wong
2023-11-07 13:36 ` Long Li [this message]
2023-11-09 12:48 ` [PATCH v3 0/3] xfs: fix two problem when recovery intents fails Chandan Babu R
2023-11-10 9:46 ` Chandan Babu R
2023-11-10 11:07 ` Long Li
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=20231107133607.GA560725@ceph-admin \
--to=leo.lilong@huaweicloud.com \
--cc=chandanbabu@kernel.org \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=houtao1@huawei.com \
--cc=linux-xfs@vger.kernel.org \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
/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.