From: Zizhi Wo <wozizhi@huawei.com>
To: <chandan.babu@oracle.com>, <djwong@kernel.org>,
<dchinner@redhat.com>, <osandov@fb.com>,
<john.g.garry@oracle.com>
Cc: <linux-xfs@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<yangerkun@huawei.com>
Subject: Re: [PATCH V3 0/2] Some bugfix for xfs fsmap
Date: Thu, 15 Aug 2024 18:20:02 +0800 [thread overview]
Message-ID: <a4a70b97-aaff-49ce-afbf-e58787647bdc@huawei.com> (raw)
In-Reply-To: <20240812011505.1414130-1-wozizhi@huawei.com>
friendly ping
在 2024/8/12 9:15, Zizhi Wo 写道:
> Changes since V2[1]:
> - Split the original patch into two, each for a different problem.
> - The fix focuses solely on addressing the omission problem and does not
> involve the precision of intervals.
>
> This patch set contains two patches to repair fsmap. Although they are both
> problems of missing query intervals, the root causes of the two are
> inconsistent, so two patches are proposed.
>
> Patch 1: The fix addresses the interval omission issue caused by the
> incorrect setting of "rm_owner" in the high_key during rmap queries. In
> this scenario, fsmap finds the record on the rmapbt, but due to the
> incorrect setting of the "rm_owner", the key of the record is larger than
> the high_key, causing the query result to be incorrect. This issue is
> resolved by fixing the "rm_owner" setup logic.
>
> Patch 2: The fix addresses the interval omission issue caused by bit
> shifting during gap queries in fsmap. In this scenario, fsmap does not
> find the record on the rmapbt, so it needs to locate it by the gap of the
> info->next_daddr and high_key address. However, due to the shift, the
> two are reduced to 0, so the query error is caused. The issue is resolved
> by introducing the "end_daddr" field in the xfs_getfsmap_info structure to
> store the high_key at the sector granularity.
>
> [1] https://lore.kernel.org/all/20240808144759.1330237-1-wozizhi@huawei.com/
>
> Zizhi Wo (2):
> xfs: Fix the owner setting issue for rmap query in xfs fsmap
> xfs: Fix missing interval for missing_owner in xfs fsmap
>
> fs/xfs/xfs_fsmap.c | 19 ++++++++++++++++++-
> 1 file changed, 18 insertions(+), 1 deletion(-)
>
prev parent reply other threads:[~2024-08-15 10:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 1:15 [PATCH V3 0/2] Some bugfix for xfs fsmap Zizhi Wo
2024-08-12 1:15 ` [PATCH V3 1/2] xfs: Fix the owner setting issue for rmap query in " Zizhi Wo
2024-08-15 16:36 ` Darrick J. Wong
2024-08-16 1:02 ` Zizhi Wo
2024-08-12 1:15 ` [PATCH V3 2/2] xfs: Fix missing interval for missing_owner " Zizhi Wo
2024-08-15 17:42 ` Darrick J. Wong
2024-08-16 1:37 ` Zizhi Wo
2024-08-15 10:20 ` Zizhi Wo [this message]
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=a4a70b97-aaff-49ce-afbf-e58787647bdc@huawei.com \
--to=wozizhi@huawei.com \
--cc=chandan.babu@oracle.com \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--cc=john.g.garry@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=osandov@fb.com \
--cc=yangerkun@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox