From: David Howells <dhowells@redhat.com>
To: Ian Kent <raven@themaw.net>
Cc: dhowells@redhat.com, Bill Davidsen <davidsen@tmr.com>,
Trond Myklebust <trond.myklebust@fys.uio.no>,
Linus Torvalds <torvalds@linux-foundation.org>,
Frank van Maarseveen <frankvm@frankvm.com>,
Hua Zhong <hzhong@gmail.com>,
"'Linux Kernel Mailing List'" <linux-kernel@vger.kernel.org>,
akpm@linux-foundation.org
Subject: Re: recent nfs change causes autofs regression
Date: Wed, 05 Sep 2007 16:37:51 +0100 [thread overview]
Message-ID: <3558.1189006671@redhat.com> (raw)
In-Reply-To: <1188996257.3119.7.camel@raven.themaw.net>
Ian Kent <raven@themaw.net> wrote:
> But what about mounting with different protocol, tcp vs udp for example.
I was referring specifically to the R/O / R/W variants of the same mount. Any
flag variation that varies the way the NFS client talks to the NFS server must
either result in a new superblock or be ignored.
David
next prev parent reply other threads:[~2007-09-05 15:39 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-30 21:07 recent nfs change causes autofs regression Hua Zhong
2007-08-30 22:37 ` Trond Myklebust
2007-08-30 22:47 ` Hua Zhong
2007-08-30 23:22 ` Trond Myklebust
2007-08-30 23:30 ` Hua Zhong
2007-08-30 23:37 ` Trond Myklebust
2007-08-30 23:44 ` Hua Zhong
2007-08-31 4:31 ` Trond Myklebust
2007-08-31 4:38 ` Linus Torvalds
2007-08-31 4:47 ` Hua Zhong
2007-08-31 4:57 ` Trond Myklebust
2007-08-31 5:09 ` Ian Kent
2007-08-31 7:50 ` Matthias Schniedermeyer
2007-08-31 1:24 ` Andrew Morton
2007-08-31 4:33 ` Trond Myklebust
2007-08-31 3:49 ` Linus Torvalds
2007-08-31 3:57 ` Hua Zhong
2007-08-31 4:44 ` Trond Myklebust
2007-08-31 4:59 ` Linus Torvalds
2007-08-31 5:04 ` Trond Myklebust
2007-08-31 5:16 ` Linus Torvalds
2007-08-31 7:40 ` Jakob Oestergaard
2007-08-31 8:07 ` Linus Torvalds
2007-08-31 8:51 ` Jakob Oestergaard
2007-08-31 16:43 ` Linus Torvalds
2007-09-03 13:20 ` Jakob Oestergaard
2007-09-03 13:43 ` Martin Knoblauch
2007-08-31 12:11 ` Trond Myklebust
2007-08-31 13:12 ` Frank van Maarseveen
2007-08-31 13:50 ` Trond Myklebust
2007-08-31 14:42 ` Frank van Maarseveen
2007-09-04 7:51 ` David Howells
2007-08-31 8:28 ` Frank van Maarseveen
2007-08-31 5:24 ` Hua Zhong
2007-08-31 5:38 ` Ian Kent
2007-08-31 8:54 ` Martin Knoblauch
2007-08-31 16:21 ` Trond Myklebust
2007-08-31 17:01 ` Linus Torvalds
2007-08-31 19:03 ` Trond Myklebust
2007-09-04 8:02 ` David Howells
2007-09-04 8:35 ` David Howells
2007-09-04 9:04 ` Linus Torvalds
2007-08-31 18:47 ` Hua Zhong
2007-08-31 19:13 ` Trond Myklebust
2007-08-31 19:35 ` Hua Zhong
2007-08-31 19:41 ` Hua Zhong
2007-09-02 0:58 ` Bill Davidsen
2007-09-04 7:54 ` David Howells
2007-09-05 12:35 ` Bill Davidsen
2007-09-05 15:34 ` David Howells
2007-09-05 12:44 ` Ian Kent
2007-09-05 15:37 ` David Howells [this message]
2007-09-05 15:50 ` Trond Myklebust
2007-09-06 5:23 ` Ian Kent
2007-09-05 16:26 ` Trond Myklebust
2007-08-31 8:14 ` Frank van Maarseveen
2007-08-31 9:05 ` Ian Kent
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=3558.1189006671@redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=davidsen@tmr.com \
--cc=frankvm@frankvm.com \
--cc=hzhong@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=raven@themaw.net \
--cc=torvalds@linux-foundation.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.