All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Whitehouse <swhiteho@redhat.com>
To: 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: [NFS] Increase size of struct fid raw buffer
Date: Mon, 07 Apr 2008 10:47:57 +0100	[thread overview]
Message-ID: <1207561677.3635.166.camel@quoit> (raw)

>From ba713d661333d790db5106c54d1f0ee94a876944 Mon Sep 17 00:00:00 2001
From: Steven Whitehouse <swhiteho@redhat.com>
Date: Mon, 7 Apr 2008 09:53:24 +0100
Subject: [PATCH] [NFS] Increase size of struct fid raw buffer

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.

Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>
Cc: Neil Brown <neilb@suse.de>
Cc: J. Bruce Fields <bfields@fieldses.org>
Cc: Adrian Bunk <bunk@kernel.org>

diff --git a/include/linux/exportfs.h b/include/linux/exportfs.h
index adcbb05..a6e928d 100644
--- a/include/linux/exportfs.h
+++ b/include/linux/exportfs.h
@@ -43,7 +43,7 @@ struct fid {
 			u32 parent_ino;
 			u32 parent_gen;
 		} i32;
-		__u32 raw[6];
+		__u32 raw[8];
 	};
 };
 
-- 
1.5.1.2




             reply	other threads:[~2008-04-07  9:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-07  9:47 Steven Whitehouse [this message]
2008-04-07 15:54 ` [NFS] Increase size of struct fid raw buffer Linus Torvalds
2008-04-08  7:50   ` Steven Whitehouse
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=1207561677.3635.166.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.