From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Hua Zhong <hzhong@gmail.com>
Cc: "'Linux Kernel Mailing List'" <linux-kernel@vger.kernel.org>,
"'Linus Torvalds'" <torvalds@linux-foundation.org>,
akpm@linux-foundation.org
Subject: RE: recent nfs change causes autofs regression
Date: Thu, 30 Aug 2007 19:37:50 -0400 [thread overview]
Message-ID: <1188517070.6626.54.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <001501c7eb5d$d295d870$77c18950$@com>
On Thu, 2007-08-30 at 16:30 -0700, Hua Zhong wrote:
> There are two disjoint directories. I am wondering why there would be cache
> coherency issues in this case? Is this Linus nfs implementation specific or
> all other Unix systems all have the same issue?
How is the NFS client to know that these directories are disjoint, or
that no-one will ever create a hard link from one directory to another?
To my knowledge, the only way to ensure this is to put them on different
disk partitions.
I don't know if all Unix systems have this issue, but I have been told
that Solaris at least has it.
> > If you know what you are doing, then there is an option which allows
> > you to override the default behaviour.
> >
> > > More importantly, it is a regression. My understanding is that unless
> > > absolutely necessary we do not introduce a "feature" that breaks
> > > working setups.
> >
> > Your turn to define what you mean by "working"? In my book that means
> > "a setup that doesn't include unexpected or unintended behaviour".
>
> "working" as in "I can mount the directory and do my work". And there has
> never been any problems as far as I know.
That is too narrow a definition: the minimum should be "everyone can
mount their directories and do their work". Your particular setup may be
safe, but that is why we have overrides: the default should be for the
kernel to be conservative, and to _tell_ users what it thinks is wrong.
> > Not being able to notice cache coherency failures on a file that is
> > mounted in two different places with two different sets of mount
> > options counts as "unexpected behaviour".
> >
> > Not being able to notice that your mount options have been overridden
> > by the kernel also counts as "unexpected behaviour".
>
> Fine. These are all very nice theories, but I just want to report this
> regression and hope it won't cause any big problems for any users out there.
> In the mean time, I am returning to 2.6.22.
Your choice.
Trond
next prev parent reply other threads:[~2007-08-30 23:38 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-30 21:07 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 [this message]
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-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 12:44 ` Ian Kent
2007-09-05 16:26 ` Trond Myklebust
2007-09-05 15:34 ` David Howells
2007-09-05 15:37 ` David Howells
2007-09-05 15:50 ` Trond Myklebust
2007-09-06 5:23 ` Ian Kent
2007-09-04 8:02 ` David Howells
2007-09-04 8:35 ` David Howells
2007-09-04 9:04 ` Linus Torvalds
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=1188517070.6626.54.camel@heimdal.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=akpm@linux-foundation.org \
--cc=hzhong@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®