From: David Howells <dhowells@redhat.com>
To: Al Viro <viro@parcelfarce.linux.theplanet.co.uk>
Cc: Bryan Henderson <hbryan@us.ibm.com>,
Christoph Hellwig <hch@infradead.org>,
"David S. Miller" <davem@davemloft.net>,
linux-fsdevel@vger.kernel.org, sfr@canb.auug.org.au,
steved@redhat.com
Subject: Re: NFS4 mount problem
Date: Mon, 18 Apr 2005 18:33:09 +0100 [thread overview]
Message-ID: <8310.1113845589@redhat.com> (raw)
In-Reply-To: <20050418171659.GE13052@parcelfarce.linux.theplanet.co.uk>
Al Viro <viro@parcelfarce.linux.theplanet.co.uk> wrote:
>
> Architecture-dependent blob passed to mount(2) (aka nfs4_mount_data).
> If you want it to be a blob, at least have a decency to use encoding
> that would not depend on alignment rules and word size. Hell, you
> could use XDR - it's not that nfs would need something new to handle
> it. Or, better yet, use a normal string.
Mount doesn't appear to permit a big enough blob though. It has a hard limit
of PAGE_SIZE.
David
next prev parent reply other threads:[~2005-04-18 17:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-15 11:57 NFS4 mount problem David Howells
2005-04-15 12:21 ` Stephen Rothwell
2005-04-15 19:51 ` Bryan Henderson
2005-04-15 20:22 ` David S. Miller
2005-04-15 22:07 ` Bryan Henderson
2005-04-17 13:55 ` Christoph Hellwig
2005-04-18 10:36 ` David Howells
2005-04-18 18:37 ` David S. Miller
2005-04-18 17:07 ` Bryan Henderson
2005-04-18 17:16 ` Al Viro
2005-04-18 17:33 ` David Howells [this message]
2005-04-18 17:43 ` Al Viro
2005-04-18 17:52 ` Bryan Henderson
2005-04-17 19:33 ` Trond Myklebust
2005-04-18 10:34 ` David Howells
2005-04-18 14:49 ` Trond Myklebust
2005-04-18 15:23 ` David Howells
2005-04-18 15:45 ` Trond Myklebust
2005-04-18 22:07 ` Bryan Henderson
2005-04-18 23:34 ` Trond Myklebust
2005-04-18 21:50 ` Bryan Henderson
2005-04-18 17:17 ` Bryan Henderson
2005-04-18 17:59 ` Trond Myklebust
2005-04-20 10:57 ` Andries Brouwer
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=8310.1113845589@redhat.com \
--to=dhowells@redhat.com \
--cc=davem@davemloft.net \
--cc=hbryan@us.ibm.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=steved@redhat.com \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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.