From: Chandan Babu R <chandanrlinux@gmail.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 3/3] xfs: make fsmap backend function key parameters const
Date: Fri, 13 Aug 2021 16:33:07 +0530 [thread overview]
Message-ID: <87eeaxli7d.fsf@garuda> (raw)
In-Reply-To: <162872993322.1220643.17973810836146274147.stgit@magnolia>
On 11 Aug 2021 at 17:58, "Darrick J. Wong" <djwong@kernel.org> wrote:
> From: Darrick J. Wong <djwong@kernel.org>
>
> There are several GETFSMAP backend functions for XFS to cover the three
> devices and various feature support. Each of these functions are passed
> pointers to the low and high keys for the dataset that userspace
> requested, and a pointer to scratchpad variables that are used to
> control the iteration and fill out records. The scratchpad data can be
> changed arbitrarily, but the keys are supposed to remain unchanged (and
> under the control of the outermost loop in xfs_getfsmap).
>
> Unfortunately, the data and rt backends modify the keys that are passed
> in from the main control loop, which causes subsequent calls to return
> incorrect query results. Specifically, each of those two functions set
> the block number in the high key to the size of their respective device.
> Since fsmap results are sorted in device number order, if the lower
> numbered device is smaller than the higher numbered device, the first
> function will set the high key to the small size, and the key remains
> unchanged as it is passed into the function for the higher numbered
> device. The second function will then fail to return all of the results
> for the dataset that userspace is asking for because the keyspace is
> incorrectly constrained.
>
Looks good.
Reviewed-by: Chandan Babu R <chandanrlinux@gmail.com>
> Signed-off-by: Darrick J. Wong <djwong@kernel.org>
> ---
> fs/xfs/xfs_fsmap.c | 30 +++++++++++++-----------------
> 1 file changed, 13 insertions(+), 17 deletions(-)
>
>
> diff --git a/fs/xfs/xfs_fsmap.c b/fs/xfs/xfs_fsmap.c
> index a0e8ab58124b..7bcc2ab68b8d 100644
> --- a/fs/xfs/xfs_fsmap.c
> +++ b/fs/xfs/xfs_fsmap.c
> @@ -61,7 +61,7 @@ xfs_fsmap_to_internal(
> static int
> xfs_fsmap_owner_to_rmap(
> struct xfs_rmap_irec *dest,
> - struct xfs_fsmap *src)
> + const struct xfs_fsmap *src)
> {
> if (!(src->fmr_flags & FMR_OF_SPECIAL_OWNER)) {
> dest->rm_owner = src->fmr_owner;
> @@ -171,7 +171,7 @@ struct xfs_getfsmap_info {
> struct xfs_getfsmap_dev {
> u32 dev;
> int (*fn)(struct xfs_trans *tp,
> - struct xfs_fsmap *keys,
> + const struct xfs_fsmap *keys,
> struct xfs_getfsmap_info *info);
> };
>
> @@ -389,7 +389,7 @@ xfs_getfsmap_datadev_bnobt_helper(
> static void
> xfs_getfsmap_set_irec_flags(
> struct xfs_rmap_irec *irec,
> - struct xfs_fsmap *fmr)
> + const struct xfs_fsmap *fmr)
> {
> irec->rm_flags = 0;
> if (fmr->fmr_flags & FMR_OF_ATTR_FORK)
> @@ -404,7 +404,7 @@ xfs_getfsmap_set_irec_flags(
> STATIC int
> xfs_getfsmap_logdev(
> struct xfs_trans *tp,
> - struct xfs_fsmap *keys,
> + const struct xfs_fsmap *keys,
> struct xfs_getfsmap_info *info)
> {
> struct xfs_mount *mp = tp->t_mountp;
> @@ -473,7 +473,7 @@ xfs_getfsmap_rtdev_rtbitmap_helper(
> STATIC int
> __xfs_getfsmap_rtdev(
> struct xfs_trans *tp,
> - struct xfs_fsmap *keys,
> + const struct xfs_fsmap *keys,
> int (*query_fn)(struct xfs_trans *,
> struct xfs_getfsmap_info *),
> struct xfs_getfsmap_info *info)
> @@ -481,16 +481,14 @@ __xfs_getfsmap_rtdev(
> struct xfs_mount *mp = tp->t_mountp;
> xfs_fsblock_t start_fsb;
> xfs_fsblock_t end_fsb;
> - xfs_daddr_t eofs;
> + uint64_t eofs;
> int error = 0;
>
> eofs = XFS_FSB_TO_BB(mp, mp->m_sb.sb_rblocks);
> if (keys[0].fmr_physical >= eofs)
> return 0;
> - if (keys[1].fmr_physical >= eofs)
> - keys[1].fmr_physical = eofs - 1;
> start_fsb = XFS_BB_TO_FSBT(mp, keys[0].fmr_physical);
> - end_fsb = XFS_BB_TO_FSB(mp, keys[1].fmr_physical);
> + end_fsb = XFS_BB_TO_FSB(mp, min(eofs - 1, keys[1].fmr_physical));
>
> /* Set up search keys */
> info->low.rm_startblock = start_fsb;
> @@ -563,7 +561,7 @@ xfs_getfsmap_rtdev_rtbitmap_query(
> STATIC int
> xfs_getfsmap_rtdev_rtbitmap(
> struct xfs_trans *tp,
> - struct xfs_fsmap *keys,
> + const struct xfs_fsmap *keys,
> struct xfs_getfsmap_info *info)
> {
> info->missing_owner = XFS_FMR_OWN_UNKNOWN;
> @@ -576,7 +574,7 @@ xfs_getfsmap_rtdev_rtbitmap(
> STATIC int
> __xfs_getfsmap_datadev(
> struct xfs_trans *tp,
> - struct xfs_fsmap *keys,
> + const struct xfs_fsmap *keys,
> struct xfs_getfsmap_info *info,
> int (*query_fn)(struct xfs_trans *,
> struct xfs_getfsmap_info *,
> @@ -591,16 +589,14 @@ __xfs_getfsmap_datadev(
> xfs_fsblock_t end_fsb;
> xfs_agnumber_t start_ag;
> xfs_agnumber_t end_ag;
> - xfs_daddr_t eofs;
> + uint64_t eofs;
> int error = 0;
>
> eofs = XFS_FSB_TO_BB(mp, mp->m_sb.sb_dblocks);
> if (keys[0].fmr_physical >= eofs)
> return 0;
> - if (keys[1].fmr_physical >= eofs)
> - keys[1].fmr_physical = eofs - 1;
> start_fsb = XFS_DADDR_TO_FSB(mp, keys[0].fmr_physical);
> - end_fsb = XFS_DADDR_TO_FSB(mp, keys[1].fmr_physical);
> + end_fsb = XFS_DADDR_TO_FSB(mp, min(eofs - 1, keys[1].fmr_physical));
>
> /*
> * Convert the fsmap low/high keys to AG based keys. Initialize
> @@ -728,7 +724,7 @@ xfs_getfsmap_datadev_rmapbt_query(
> STATIC int
> xfs_getfsmap_datadev_rmapbt(
> struct xfs_trans *tp,
> - struct xfs_fsmap *keys,
> + const struct xfs_fsmap *keys,
> struct xfs_getfsmap_info *info)
> {
> info->missing_owner = XFS_FMR_OWN_FREE;
> @@ -763,7 +759,7 @@ xfs_getfsmap_datadev_bnobt_query(
> STATIC int
> xfs_getfsmap_datadev_bnobt(
> struct xfs_trans *tp,
> - struct xfs_fsmap *keys,
> + const struct xfs_fsmap *keys,
> struct xfs_getfsmap_info *info)
> {
> struct xfs_alloc_rec_incore akeys[2];
--
chandan
prev parent reply other threads:[~2021-08-13 11:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-12 0:58 [PATCHSET 0/3] xfs: fix various bugs in fsmap Darrick J. Wong
2021-08-12 0:58 ` [PATCH 1/3] xfs: make xfs_rtalloc_query_range input parameters const Darrick J. Wong
2021-08-12 8:30 ` Christoph Hellwig
2021-08-12 15:07 ` Darrick J. Wong
2021-08-13 9:56 ` Chandan Babu R
2021-08-12 0:58 ` [PATCH 2/3] xfs: fix off-by-one error when the last rt extent is in use Darrick J. Wong
2021-08-12 8:36 ` Christoph Hellwig
2021-08-12 16:24 ` Darrick J. Wong
2021-08-13 10:50 ` Chandan Babu R
2021-08-13 16:16 ` Darrick J. Wong
2021-08-12 0:58 ` [PATCH 3/3] xfs: make fsmap backend function key parameters const Darrick J. Wong
2021-08-12 8:40 ` Christoph Hellwig
2021-08-13 11:03 ` Chandan Babu R [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=87eeaxli7d.fsf@garuda \
--to=chandanrlinux@gmail.com \
--cc=djwong@kernel.org \
--cc=linux-xfs@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).