From: Steve Dickson <SteveD@redhat.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Linux NFS Mailing list <linux-nfs@vger.kernel.org>,
Linux NFSv4 mailing list <nfsv4@linux-nfs.org>
Subject: Re: [PATCH 2/2] Enable v4 mounts when either "nfsvers=4" or "vers=4" option are set (vers-02)
Date: Thu, 27 Aug 2009 10:14:42 -0400 [thread overview]
Message-ID: <4A9694D2.2030205@RedHat.com> (raw)
In-Reply-To: <1251316764.5226.21.camel@heimdal.trondhjem.org>
On 08/26/2009 03:59 PM, Trond Myklebust wrote:
> On Wed, 2009-08-26 at 15:50 -0400, Chuck Lever wrote:
>> Yeah, switching file system types in the mount(2) system call is the
>> fly in the ointment. I'm just wondering if Trond had some thoughts
>> about making that more feasible.
>
> Just look at what we're already doing for NFSv4. Inside nfs4_get_sb, we
> basically do a kernel mount in order to get the real super block. We
> then simply have to attach it to the vfsmount that the sys_mount() call
> passed down to us.
Well its not nfs4_get_sb() that would have to change its nfs_get_sb()
that would have to do an nfs4 mount after it discovered the -o vers=4.
It would get very messy very quickly for absolutely no reason since
the propose mount patch is straightforward, it works and better yet
its done! ;-)
>
> This really isn't anything new or difficult...
Granted, mounting from the kernel is not new, but giving sys_mount()
on file system type which ends up mounting a complete different
file system is new... Plus architecturally that just seems wrong...
A abit incestual... would you say! ;-)
I say we go with the proposed patch since its simple, architecturally
sound, will not cause problems down the road as long as nfs4 remains
a standalone file system and its done! Plus I have a patch waiting
in the wings that actually does make v4 the first mount that is
tried... making v4 the default version...
steved.
next prev parent reply other threads:[~2009-08-27 14:14 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-25 17:52 [PATCH 0/2] Enable v4 mounts when either "nfsvers=4" or "vers=4" option are set (vers-02) Steve Dickson
2009-08-25 17:54 ` [PATCH 1/2] " Steve Dickson
[not found] ` <4A9424DB.2040303-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2009-08-25 17:55 ` [PATCH 2/2] " Steve Dickson
2009-08-25 18:59 ` Chuck Lever
2009-08-25 19:18 ` Steve Dickson
2009-08-25 19:32 ` Chuck Lever
2009-08-25 20:15 ` Steve Dickson
2009-08-25 20:37 ` Chuck Lever
2009-08-26 12:10 ` Steve Dickson
2009-08-25 20:49 ` Trond Myklebust
2009-08-26 12:28 ` Steve Dickson
2009-08-26 14:20 ` Chuck Lever
2009-08-26 15:07 ` Steve Dickson
2009-08-26 16:35 ` Chuck Lever
2009-08-26 17:08 ` Steve Dickson
2009-08-26 17:22 ` Chuck Lever
2009-08-26 17:51 ` Steve Dickson
2009-08-26 19:50 ` Chuck Lever
2009-08-26 19:59 ` Trond Myklebust
2009-08-27 14:14 ` Steve Dickson [this message]
2009-08-27 17:32 ` Chuck Lever
2009-08-28 2:55 ` Steve Dickson
2009-08-28 16:12 ` Christoph Hellwig
2009-08-28 16:35 ` Steve Dickson
[not found] ` <4A980751.7070206-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2009-08-28 16:41 ` Christoph Hellwig
2009-08-28 16:44 ` Chuck Lever
2009-08-28 16:53 ` Steve Dickson
2009-08-28 16:59 ` Christoph Hellwig
2009-08-28 17:19 ` Steve Dickson
2009-08-27 17:48 ` Trond Myklebust
2009-08-27 17:58 ` Chuck Lever
2009-08-27 19:28 ` Steve Dickson
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=4A9694D2.2030205@RedHat.com \
--to=steved@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=nfsv4@linux-nfs.org \
--cc=trond.myklebust@fys.uio.no \
/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.