From: Christoph Hellwig <hch@infradead.org>
To: "David S. Miller" <davem@davemloft.net>
Cc: Bryan Henderson <hbryan@us.ibm.com>,
sfr@canb.auug.org.au, dhowells@redhat.com,
linux-fsdevel@vger.kernel.org,
linux-fsdevel-owner@vger.kernel.org, steved@redhat.com
Subject: Re: NFS4 mount problem
Date: Sun, 17 Apr 2005 14:55:21 +0100 [thread overview]
Message-ID: <20050417135521.GA6876@infradead.org> (raw)
In-Reply-To: <20050415132259.24c3d570.davem@davemloft.net>
On Fri, Apr 15, 2005 at 01:22:59PM -0700, David S. Miller wrote:
>
> Make a ->compat_read_super() just like we have a ->compat_ioctl()
> method for files, if you want to suggest a solution like what
> you describe.
I don't think we should encourage filesystem writers to do such stupid
things as ncfps/smbfs do. In fact I'm totally unhappy thay nfs4 went
down that road.
next prev parent reply other threads:[~2005-04-17 13:56 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 [this message]
2005-04-18 17:07 ` Bryan Henderson
2005-04-18 17:16 ` Al Viro
2005-04-18 17:33 ` David Howells
2005-04-18 17:43 ` Al Viro
2005-04-18 17:52 ` Bryan Henderson
2005-04-18 10:36 ` David Howells
2005-04-18 18:37 ` David S. Miller
2005-04-17 19:33 ` Trond Myklebust
2005-04-18 17:17 ` Bryan Henderson
2005-04-18 17:59 ` Trond Myklebust
2005-04-20 10:57 ` Andries Brouwer
2005-04-18 10:34 ` David Howells
2005-04-18 14:49 ` Trond Myklebust
2005-04-18 22:07 ` Bryan Henderson
2005-04-18 23:34 ` Trond Myklebust
2005-04-18 15:23 ` David Howells
2005-04-18 15:45 ` Trond Myklebust
2005-04-18 21:50 ` Bryan Henderson
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=20050417135521.GA6876@infradead.org \
--to=hch@infradead.org \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=hbryan@us.ibm.com \
--cc=linux-fsdevel-owner@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).