From: Steven Whitehouse <swhiteho@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>, Neil Brown <neilb@suse.de>,
"J. Bruce Fields" <bfields@fieldses.org>,
Adrian Bunk <bunk@kernel.org>
Subject: Re: [NFS] Increase size of struct fid raw buffer
Date: Tue, 08 Apr 2008 08:50:05 +0100 [thread overview]
Message-ID: <1207641005.3635.238.camel@quoit> (raw)
In-Reply-To: <alpine.LFD.1.00.0804070850310.11277@woody.linux-foundation.org>
Hi,
On Mon, 2008-04-07 at 08:54 -0700, Linus Torvalds wrote:
>
> On Mon, 7 Apr 2008, Steven Whitehouse wrote:
> >
> > GFS2 requires the NFS filehandle buffer to be larger than the
> > minimum size as per the bug report: http://lkml.org/lkml/2007/10/24/374
> > Its a pretty trivial fix for now and I've done a test which shows
> > that it works ok.
>
> I'm not seeing the point of this.
>
> Every single instance of "struct fid" that I saw in a quick grep was
> created not as a "struct fid", but as some other data structure that was
> then cast to a "struct fid *".
>
> So the _underlying_ size of "struct fid" seems to be pretty random, and
> totally unrelated to this declaration.
>
> But admittedly that really was just a quick grep, and maybe I missed
> something. But it seems like this patch doesn't really change anything,
> just largely makes a change in a structure that is apparently used as an
> opaque pointer.
>
> Is there anything that actually uses "struct fid" as an _allocation_
> entity?
>
> And if not, then that "_u32 raw[6]" should probably be a un-sized "_u32
> raw[]" instead, no?
>
> Linus
I'm happy with that solution, although I'd assumed that the reason this
field had a size in the first place was that the NFS people had a plan
to use the structure as an allocation entity in the future. Can an NFS
developer please confirm/deny this?
If everybody is happy with the plan, then I'll send a patch to make the
change as you suggest shortly,
Steve.
next prev parent reply other threads:[~2008-04-08 7:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-07 9:47 [NFS] Increase size of struct fid raw buffer Steven Whitehouse
2008-04-07 15:54 ` Linus Torvalds
2008-04-08 7:50 ` Steven Whitehouse [this message]
2008-04-08 7:58 ` Christoph Hellwig
2008-04-08 9:57 ` Steven Whitehouse
2008-04-08 13:01 ` [NFS] Use a zero sized array for raw field in struct fid Steven Whitehouse
2008-04-09 16:13 ` J. Bruce Fields
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=1207641005.3635.238.camel@quoit \
--to=swhiteho@redhat.com \
--cc=bfields@fieldses.org \
--cc=bunk@kernel.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=torvalds@linux-foundation.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 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.