From: Jim Rees <rees@umich.edu>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: "Yong, Fan" <fan.yong@intel.com>, Peng Tao <bergwolf@gmail.com>,
"Dilger, Andreas" <andreas.dilger@intel.com>,
"J. Bruce Fields" <bfields@fieldses.org>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
Steve Dickson <steved@redhat.com>
Subject: Re: [PATCH] nfs: support 64-bit root inode number in NFS FSID
Date: Thu, 23 May 2013 10:20:10 -0400 [thread overview]
Message-ID: <20130523142010.GA3634@umich.edu> (raw)
In-Reply-To: <1369316375.3764.7.camel@leira.trondhjem.org>
Myklebust, Trond wrote:
On Thu, 2013-05-23 at 12:59 +0000, Yong, Fan wrote:
> Just make it match the "inode64" in nfs-utils parse_fsid(), which is defined as "unsigned long long", and the parsed_fsid:: inode is copied from "inode64" as following:
>
> static int parse_fsid(int fsidtype, int fsidlen, char *fsid,
> struct parsed_fsid *parsed)
> {
> unsigned int dev;
> unsigned long long inode64;
> ...
> case FSID_UUID16_INUM: /* 8 byte inode number and 16 byte uuid */
> if (fsidlen != 24)
> return -1;
> memcpy(&inode64, fsid, 8);
> parsed->inode = inode64;
> parsed->uuidlen = 16;
> parsed->fhuuid = fsid+8;
> break;
> }
>
> --
> Cheers,
> Nasf
Eeeeeeeewww! This is _exactly_ why we should be using properly
dimensioned types. Feel free to tell me how the value of 'inode64' is
well defined on systems where sizeof(unsigned long long) != 8...
Is there any reason not to use ino_t?
next prev parent reply other threads:[~2013-05-23 14:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 23:06 [PATCH] nfs: support 64-bit root inode number in NFS FSID Dilger, Andreas
2013-05-23 8:12 ` Peng Tao
2013-05-23 12:49 ` Myklebust, Trond
2013-05-23 12:59 ` Yong, Fan
2013-05-23 13:39 ` Myklebust, Trond
2013-05-23 14:20 ` Jim Rees [this message]
2013-05-23 14:21 ` Myklebust, Trond
2013-05-24 1:30 ` Yong, Fan
2013-05-24 1:49 ` Myklebust, Trond
2013-06-03 1:59 ` Yong, Fan
2013-06-03 2:02 ` Yong, Fan
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=20130523142010.GA3634@umich.edu \
--to=rees@umich.edu \
--cc=Trond.Myklebust@netapp.com \
--cc=andreas.dilger@intel.com \
--cc=bergwolf@gmail.com \
--cc=bfields@fieldses.org \
--cc=fan.yong@intel.com \
--cc=linux-nfs@vger.kernel.org \
--cc=steved@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.