From: "Darrick J. Wong" <djwong@kernel.org>
To: Dave Chinner <david@fromorbit.com>
Cc: Catherine Hoang <catherine.hoang@oracle.com>,
linux-xfs@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: [PATCH v2 2/2] xfs: add FS_IOC_GETFSUUID ioctl
Date: Mon, 21 Nov 2022 14:18:47 -0800 [thread overview]
Message-ID: <Y3v5R+FlFf5KvLsb@magnolia> (raw)
In-Reply-To: <20221121210223.GJ3600936@dread.disaster.area>
On Tue, Nov 22, 2022 at 08:02:23AM +1100, Dave Chinner wrote:
> On Fri, Nov 18, 2022 at 01:14:08PM -0800, Catherine Hoang wrote:
> > Add a new ioctl to retrieve the UUID of a mounted xfs filesystem. This is a
> > precursor to adding the SETFSUUID ioctl.
> >
> > Signed-off-by: Catherine Hoang <catherine.hoang@oracle.com>
> > Reviewed-by: Allison Henderson <allison.henderson@oracle.com>
> > ---
> > fs/xfs/xfs_ioctl.c | 36 ++++++++++++++++++++++++++++++++++++
> > 1 file changed, 36 insertions(+)
> >
> > diff --git a/fs/xfs/xfs_ioctl.c b/fs/xfs/xfs_ioctl.c
> > index 1f783e979629..cf77715afe9e 100644
> > --- a/fs/xfs/xfs_ioctl.c
> > +++ b/fs/xfs/xfs_ioctl.c
> > @@ -1865,6 +1865,39 @@ xfs_fs_eofblocks_from_user(
> > return 0;
> > }
> >
> > +static int
> > +xfs_ioctl_getuuid(
> > + struct xfs_mount *mp,
> > + struct fsuuid __user *ufsuuid)
> > +{
> > + struct fsuuid fsuuid;
> > + __u8 uuid[UUID_SIZE];
>
> uuid_t, please, not an open coded uuid_t.
>
> > +
> > + if (copy_from_user(&fsuuid, ufsuuid, sizeof(fsuuid)))
> > + return -EFAULT;
>
> I still think this failing to copy the flex array member and then
> having to declare a local uuid buffer is an ugly wart, not just on
> the API side of things.
>
> > + if (fsuuid.fsu_len == 0) {
> > + fsuuid.fsu_len = UUID_SIZE;
>
> XFS uses sizeof(uuid_t) for the size of it's uuids, not UUID_SIZE.
>
> > + if (copy_to_user(&ufsuuid->fsu_len, &fsuuid.fsu_len,
> > + sizeof(fsuuid.fsu_len)))
> > + return -EFAULT;
> > + return 0;
> > + }
> > +
> > + if (fsuuid.fsu_len < UUID_SIZE || fsuuid.fsu_flags != 0)
> > + return -EINVAL;
> > +
> > + spin_lock(&mp->m_sb_lock);
> > + memcpy(uuid, &mp->m_sb.sb_uuid, UUID_SIZE);
> > + spin_unlock(&mp->m_sb_lock);
>
> Hmmmm. Shouldn't we be promoting xfs_fs_get_uuid() to xfs_super.c
> (without the pNFS warning!) and calling that here, rather than open
> coding another "get the XFS superblock UUID" function here?
I disagree that it's worth the effort to create a helper function to
wrap four lines of code, particularly since the pnfs code has this extra
weird wart of returning the byte offset(?) of the uuid location.
> i.e.
> if (fsuuid.fsu_flags != 0)
> return -EINVAL;
>
> error = xfs_fs_get_uuid(&mp->m_sb, uuid, &fsuuid.fsu_len, NULL);
> if (error)
> return -EINVAL;
>
> Also, uuid_copy()?
Why does xfs_fs_get_uuid use memcpy then? Did the compiler reject the
u8* -> uuid_t * type conversion?
Alternately there's export_uuid().
--D
> Cheers,
>
> Dave.
>
> --
> Dave Chinner
> david@fromorbit.com
next prev parent reply other threads:[~2022-11-21 22:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 21:14 [PATCH v2 0/2] porting the GETFSUUID ioctl to xfs Catherine Hoang
2022-11-18 21:14 ` [PATCH v2 1/2] fs: hoist get/set UUID ioctls Catherine Hoang
2022-11-21 21:14 ` Dave Chinner
2022-11-18 21:14 ` [PATCH v2 2/2] xfs: add FS_IOC_GETFSUUID ioctl Catherine Hoang
2022-11-21 18:05 ` Darrick J. Wong
2022-11-21 21:02 ` Dave Chinner
2022-11-21 22:18 ` Darrick J. Wong [this message]
2022-11-21 23:20 ` Dave Chinner
2022-11-21 21:15 ` [PATCH v2 0/2] porting the GETFSUUID ioctl to xfs 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=Y3v5R+FlFf5KvLsb@magnolia \
--to=djwong@kernel.org \
--cc=catherine.hoang@oracle.com \
--cc=david@fromorbit.com \
--cc=linux-ext4@vger.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