linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brian Foster <bfoster@redhat.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 11/13] xfs: return the hash value of a leaf1 directory block
Date: Thu, 8 Jun 2017 12:31:50 -0400	[thread overview]
Message-ID: <20170608163147.GG5244@bfoster.bfoster> (raw)
In-Reply-To: <20170608155359.GI4530@birch.djwong.org>

On Thu, Jun 08, 2017 at 08:53:59AM -0700, Darrick J. Wong wrote:
> On Thu, Jun 08, 2017 at 09:02:26AM -0400, Brian Foster wrote:
> > On Fri, Jun 02, 2017 at 02:25:08PM -0700, Darrick J. Wong wrote:
> > > From: Darrick J. Wong <darrick.wong@oracle.com>
> > > 
> > > Provide a way to calculate the highest hash value of a leaf1 block.
> > > This will be used by the directory scrubbing code to check the sanity
> > > of hashes in leaf1 directory blocks.
> > > 
> > > Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> > > ---
> > >  fs/xfs/libxfs/xfs_dir2_node.c |   28 ++++++++++++++++++++++++++++
> > >  fs/xfs/libxfs/xfs_dir2_priv.h |    2 ++
> > >  2 files changed, 30 insertions(+)
> > > 
> > > 
> > > diff --git a/fs/xfs/libxfs/xfs_dir2_node.c b/fs/xfs/libxfs/xfs_dir2_node.c
> > > index bbd1238..15c1881 100644
> > > --- a/fs/xfs/libxfs/xfs_dir2_node.c
> > > +++ b/fs/xfs/libxfs/xfs_dir2_node.c
> > > @@ -524,6 +524,34 @@ xfs_dir2_free_hdr_check(
> > >  #endif	/* DEBUG */
> > >  
> > >  /*
> > > + * Return the last hash value in the leaf1.
> > > + * Stale entries are ok.
> > > + */
> > > +xfs_dahash_t					/* hash value */
> > > +xfs_dir2_leaf1_lasthash(
> > > +	struct xfs_inode	*dp,
> > > +	struct xfs_buf		*bp,		/* leaf buffer */
> > > +	int			*count)		/* count of entries in leaf */
> > > +{
> > > +	struct xfs_dir2_leaf	*leaf = bp->b_addr;
> > > +	struct xfs_dir2_leaf_entry *ents;
> > > +	struct xfs_dir3_icleaf_hdr leafhdr;
> > > +
> > > +	dp->d_ops->leaf_hdr_from_disk(&leafhdr, leaf);
> > > +
> > > +	ASSERT(leafhdr.magic == XFS_DIR2_LEAF1_MAGIC ||
> > > +	       leafhdr.magic == XFS_DIR3_LEAF1_MAGIC);
> > > +
> > 
> > It looks like the assert is the only difference between this function
> > and xfs_dir2_leafn_lasthash(). It seems like overkill to me to duplicate
> > just for that. How about we fix up the assert to cover the additional
> > magics (and maybe rename _leafn_lasthash() to _leaf_lasthash() if
> > appropriate)?
> > 
> > Actually, taking a closer look, ->leaf_hdr_from_disk() already asserts
> > on the appropriate LEAF1/LEAFN magic based on the callback that is
> > specified. ISTM that we could also just kill the _lasthash() assert.
> 
> The ASSERTs in the _lasthash functions and in leaf_hdr_from_disk aren't
> testing quite the same things.  The asserts in _dir2_leaf[1n]_lasthash
> check that we actually passed it a leaf1 or leafn block, respectively.
> The asserts in _dir[23]_leaf_hdr_from_disk check that we actually fed it
> a dir2 or dir3 leaf* block without caring whether it's leaf1 or leafn.
> That's why I didn't just get rid of the assert and rename the function
> xfs_dir2_leaf_lasthash().
> 

Yeah, I'm aware they are not exactly equivalent. I was more thinking
that we still have some assert protection if something is blatantly
wrong (i.e., corruption, some non dir block, etc.). As it is, if the
_leaf1_lasthash() assert fails because we passed a leafn block to the
function, the solution presumably is to use the leafn function that
basically does the same thing (modulo the assert), right?

In other words, what's the value of asserting on the magics between two
functions that handle either format in the exact same way? If there is
value somewhere, it sounds like perhaps it's to the benefit of the
caller than for the helper itself (which is reasonable, I think, but
still doesn't justify the duplication IMO).

> I suppose we could just make a single parent function that takes the two
> magics it wants to see and have _dir2_leaf[1n]_lasthash call the parent
> function with the magic numbers they want to check.  How does that
> sound?
> 

Do I understand correctly that you mean an "internal" function that
receives the expected magic as a param (for the assert) and a couple
leaf[1|n]_lasthash() wrappers that pass the associated LEAF[1|N] magics?
If so, that sounds reasonable to me if you'd really prefer to keep the
isolated asserts. I'm more just trying to avoid the code duplication.

Brian

> --D
> 
> > 
> > Brian
> > 
> > > +	if (count)
> > > +		*count = leafhdr.count;
> > > +	if (!leafhdr.count)
> > > +		return 0;
> > > +
> > > +	ents = dp->d_ops->leaf_ents_p(leaf);
> > > +	return be32_to_cpu(ents[leafhdr.count - 1].hashval);
> > > +}
> > > +
> > > +/*
> > >   * Return the last hash value in the leaf.
> > >   * Stale entries are ok.
> > >   */
> > > diff --git a/fs/xfs/libxfs/xfs_dir2_priv.h b/fs/xfs/libxfs/xfs_dir2_priv.h
> > > index 576f2d2..c09bca1 100644
> > > --- a/fs/xfs/libxfs/xfs_dir2_priv.h
> > > +++ b/fs/xfs/libxfs/xfs_dir2_priv.h
> > > @@ -95,6 +95,8 @@ extern bool xfs_dir3_leaf_check_int(struct xfs_mount *mp, struct xfs_inode *dp,
> > >  /* xfs_dir2_node.c */
> > >  extern int xfs_dir2_leaf_to_node(struct xfs_da_args *args,
> > >  		struct xfs_buf *lbp);
> > > +extern xfs_dahash_t xfs_dir2_leaf1_lasthash(struct xfs_inode *dp,
> > > +		struct xfs_buf *bp, int *count);
> > >  extern xfs_dahash_t xfs_dir2_leafn_lasthash(struct xfs_inode *dp,
> > >  		struct xfs_buf *bp, int *count);
> > >  extern int xfs_dir2_leafn_lookup_int(struct xfs_buf *bp,
> > > 
> > > --
> > > To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> > > the body of a message to majordomo@vger.kernel.org
> > > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2017-06-08 16:31 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-02 21:24 [PATCH v7 00/13] xfs: preparing for online scrub support Darrick J. Wong
2017-06-02 21:24 ` [PATCH 01/13] xfs: optimize _btree_query_all Darrick J. Wong
2017-06-06 13:32   ` Brian Foster
2017-06-06 17:43     ` Darrick J. Wong
2017-06-07  1:18   ` [PATCH v2 " Darrick J. Wong
2017-06-07 14:22     ` Brian Foster
2017-06-02 21:24 ` [PATCH 02/13] xfs: remove double-underscore integer types Darrick J. Wong
2017-06-02 21:24 ` [PATCH 03/13] xfs: always compile the btree inorder check functions Darrick J. Wong
2017-06-06 13:32   ` Brian Foster
2017-06-02 21:24 ` [PATCH 04/13] xfs: export various function for the online scrubber Darrick J. Wong
2017-06-06 13:32   ` Brian Foster
2017-06-02 21:24 ` [PATCH 05/13] xfs: plumb in needed functions for range querying of various btrees Darrick J. Wong
2017-06-06 13:33   ` Brian Foster
2017-06-02 21:24 ` [PATCH 06/13] xfs: export _inobt_btrec_to_irec and _ialloc_cluster_alignment for scrub Darrick J. Wong
2017-06-06 16:27   ` Brian Foster
2017-06-06 17:46     ` Darrick J. Wong
2017-06-02 21:24 ` [PATCH 07/13] xfs: check if an inode is cached and allocated Darrick J. Wong
2017-06-06 16:28   ` Brian Foster
2017-06-06 18:40     ` Darrick J. Wong
2017-06-07 14:22       ` Brian Foster
2017-06-15  5:00         ` Darrick J. Wong
2017-06-07  1:21   ` [PATCH v2 " Darrick J. Wong
2017-06-16 17:59   ` [PATCH v3 " Darrick J. Wong
2017-06-19 12:07     ` Brian Foster
2017-06-02 21:24 ` [PATCH 08/13] xfs: reflink find shared should take a transaction Darrick J. Wong
2017-06-06 16:28   ` Brian Foster
2017-06-02 21:24 ` [PATCH 09/13] xfs: separate function to check if reflink flag needed Darrick J. Wong
2017-06-06 16:28   ` Brian Foster
2017-06-06 18:05     ` Darrick J. Wong
2017-06-07  1:26   ` [PATCH v2 " Darrick J. Wong
2017-06-07 14:22     ` Brian Foster
2017-06-02 21:25 ` [PATCH 10/13] xfs: refactor the ifork block counting function Darrick J. Wong
2017-06-06 16:29   ` Brian Foster
2017-06-06 18:51     ` Darrick J. Wong
2017-06-06 20:35       ` Darrick J. Wong
2017-06-07  1:29   ` [PATCH v2 9.9/13] xfs: make _bmap_count_blocks consistent wrt delalloc extent behavior Darrick J. Wong
2017-06-07 15:11     ` Brian Foster
2017-06-07 16:19       ` Darrick J. Wong
2017-06-07  1:29   ` [PATCH v2 10/13] xfs: refactor the ifork block counting function Darrick J. Wong
2017-06-07 15:11     ` Brian Foster
2017-06-02 21:25 ` [PATCH 11/13] xfs: return the hash value of a leaf1 directory block Darrick J. Wong
2017-06-08 13:02   ` Brian Foster
2017-06-08 15:53     ` Darrick J. Wong
2017-06-08 16:31       ` Brian Foster [this message]
2017-06-08 16:43         ` Darrick J. Wong
2017-06-08 16:52           ` Brian Foster
2017-06-08 18:22   ` [PATCH v2 " Darrick J. Wong
2017-06-09 12:54     ` Brian Foster
2017-06-02 21:25 ` [PATCH 12/13] xfs: pass along transaction context when reading directory block buffers Darrick J. Wong
2017-06-08 13:02   ` Brian Foster
2017-06-02 21:25 ` [PATCH 13/13] xfs: pass along transaction context when reading xattr " Darrick J. Wong
2017-06-08 13:02   ` Brian Foster
2017-06-02 22:19 ` [PATCH 14/13] xfs: allow reading of already-locked remote symbolic link Darrick J. Wong
2017-06-08 13:02   ` Brian Foster
2017-06-26  6:04 ` [PATCH 15/13] xfs: grab dquots without taking the ilock Darrick J. Wong
2017-06-27 11:00   ` Brian Foster

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=20170608163147.GG5244@bfoster.bfoster \
    --to=bfoster@redhat.com \
    --cc=darrick.wong@oracle.com \
    --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).