public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 2/2] xfs: constify xfs_name_dotdot
Date: Wed, 9 Mar 2022 15:27:40 -0800	[thread overview]
Message-ID: <20220309232740.GD8224@magnolia> (raw)
In-Reply-To: <20220309223245.GK661808@dread.disaster.area>

On Thu, Mar 10, 2022 at 09:32:45AM +1100, Dave Chinner wrote:
> On Wed, Mar 09, 2022 at 11:22:47AM -0800, Darrick J. Wong wrote:
> > From: Darrick J. Wong <djwong@kernel.org>
> > 
> > The symbol xfs_name_dotdot is a global variable that the xfs codebase
> > uses here and there to look up directory dotdot entries.  Currently it's
> > a non-const variable, which means that it's a mutable global variable.
> > So far nobody's abused this to cause problems, but let's use the
> > compiler to enforce that.
> > 
> > Signed-off-by: Darrick J. Wong <djwong@kernel.org>
> > ---
> >  fs/xfs/libxfs/xfs_dir2.c |    6 +++++-
> >  fs/xfs/libxfs/xfs_dir2.h |    2 +-
> >  fs/xfs/scrub/parent.c    |    6 ++++--
> >  fs/xfs/xfs_export.c      |    3 ++-
> >  4 files changed, 12 insertions(+), 5 deletions(-)
> > 
> > 
> > diff --git a/fs/xfs/libxfs/xfs_dir2.c b/fs/xfs/libxfs/xfs_dir2.c
> > index a77d931d65a3..cf9fa07e62d5 100644
> > --- a/fs/xfs/libxfs/xfs_dir2.c
> > +++ b/fs/xfs/libxfs/xfs_dir2.c
> > @@ -19,7 +19,11 @@
> >  #include "xfs_error.h"
> >  #include "xfs_trace.h"
> >  
> > -struct xfs_name xfs_name_dotdot = { (unsigned char *)"..", 2, XFS_DIR3_FT_DIR };
> > +const struct xfs_name xfs_name_dotdot = {
> > +	.name	= (unsigned char *)"..",
> > +	.len	= 2,
> > +	.type	= XFS_DIR3_FT_DIR,
> > +};
> 
> *nod*
> 
> > diff --git a/fs/xfs/scrub/parent.c b/fs/xfs/scrub/parent.c
> > index ab182a5cd0c0..e9549d998cdc 100644
> > --- a/fs/xfs/scrub/parent.c
> > +++ b/fs/xfs/scrub/parent.c
> > @@ -131,6 +131,7 @@ xchk_parent_validate(
> >  	xfs_ino_t		dnum,
> >  	bool			*try_again)
> >  {
> > +	struct xfs_name		dotdot = xfs_name_dotdot;
> >  	struct xfs_mount	*mp = sc->mp;
> >  	struct xfs_inode	*dp = NULL;
> >  	xfs_nlink_t		expected_nlink;
> > @@ -230,7 +231,7 @@ xchk_parent_validate(
> >  	expected_nlink = VFS_I(sc->ip)->i_nlink == 0 ? 0 : 1;
> >  
> >  	/* Look up '..' to see if the inode changed. */
> > -	error = xfs_dir_lookup(sc->tp, sc->ip, &xfs_name_dotdot, &dnum, NULL);
> > +	error = xfs_dir_lookup(sc->tp, sc->ip, &dotdot, &dnum, NULL);
> >  	if (!xchk_fblock_process_error(sc, XFS_DATA_FORK, 0, &error))
> >  		goto out_rele;
> >  
> 
> Why can't xfs_dir_lookup() be defined as a const xname for the input
> name? All it does is extract the contents into the da_args fields,
> and pass it to xfs_dir_hashname() which you converted to const in
> the previous patch.

The metadata directory patchset changes xfs_dir_lookup to return the
ftype in the dirent so that it can bail early if the dirent doesn't
point to the filetype that we want.

I wouldn't be /that/ sad to remove that bit of functionality in favor of
constifying the name parameter to xfs_dir_lookup.

Thinking about this more, I think the metadir code could implement its
own lookup dispatch function that /does/ return the dirent ftype, since
the sf/block/node/leaf functions all live in libxfs anyway.

> Or does the compiler then complain at all the other callsites that
> you're passing non-const stuff to const function parameters? i.e. am
> I just pulling on another dangling end of the ball of string at this
> point?

Nope, just djwong-dev blindness. :(

> > @@ -263,6 +264,7 @@ int
> >  xchk_parent(
> >  	struct xfs_scrub	*sc)
> >  {
> > +	struct xfs_name		dotdot = xfs_name_dotdot;
> >  	struct xfs_mount	*mp = sc->mp;
> >  	xfs_ino_t		dnum;
> >  	bool			try_again;
> > @@ -293,7 +295,7 @@ xchk_parent(
> >  	xfs_iunlock(sc->ip, XFS_ILOCK_EXCL | XFS_MMAPLOCK_EXCL);
> >  
> >  	/* Look up '..' */
> > -	error = xfs_dir_lookup(sc->tp, sc->ip, &xfs_name_dotdot, &dnum, NULL);
> > +	error = xfs_dir_lookup(sc->tp, sc->ip, &dotdot, &dnum, NULL);
> >  	if (!xchk_fblock_process_error(sc, XFS_DATA_FORK, 0, &error))
> >  		goto out;
> >  	if (!xfs_verify_dir_ino(mp, dnum)) {
> > diff --git a/fs/xfs/xfs_export.c b/fs/xfs/xfs_export.c
> > index 1064c2342876..8939119191f4 100644
> > --- a/fs/xfs/xfs_export.c
> > +++ b/fs/xfs/xfs_export.c
> > @@ -206,10 +206,11 @@ STATIC struct dentry *
> >  xfs_fs_get_parent(
> >  	struct dentry		*child)
> >  {
> > +	struct xfs_name		dotdot = xfs_name_dotdot;
> >  	int			error;
> >  	struct xfs_inode	*cip;
> >  
> > -	error = xfs_lookup(XFS_I(d_inode(child)), &xfs_name_dotdot, &cip, NULL);
> > +	error = xfs_lookup(XFS_I(d_inode(child)), &dotdot, &cip, NULL);
> >  	if (unlikely(error))
> >  		return ERR_PTR(error);
> 
> This only calls xfs_dir_lookup() with name, so if xfs_dir_lookup()
> can have a const name, so can xfs_lookup()....

Yep.  I'll fix that in the next version.

--D

> Cheers,
> 
> Dave.
> -- 
> Dave Chinner
> david@fromorbit.com

  reply	other threads:[~2022-03-09 23:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-09 19:22 [PATCHSET 0/2] xfs: constify dotdot global variable Darrick J. Wong
2022-03-09 19:22 ` [PATCH 1/2] xfs: constify the name argument to various directory functions Darrick J. Wong
2022-03-09 22:06   ` Dave Chinner
2022-03-09 19:22 ` [PATCH 2/2] xfs: constify xfs_name_dotdot Darrick J. Wong
2022-03-09 22:32   ` Dave Chinner
2022-03-09 23:27     ` Darrick J. Wong [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-03-10 21:53 [PATCHSET v2 0/2] xfs: constify dotdot global variable Darrick J. Wong
2022-03-10 21:53 ` [PATCH 2/2] xfs: constify xfs_name_dotdot Darrick J. Wong
2022-03-10 22:26   ` Dave Chinner

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=20220309232740.GD8224@magnolia \
    --to=djwong@kernel.org \
    --cc=david@fromorbit.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