From: ebiederm@xmission.com (Eric W. Biederman)
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Alexey Dobriyan <adobriyan@gmail.com>,
rjw@sisk.pl, trond.myklebust@fys.uio.no, gnome42@gmail.com,
linux-kernel@vger.kernel.org, bfields@fieldses.org,
den@openvz.org
Subject: Re: 2.6.24-rc3-git4 NFS crossmnt regression
Date: Fri, 07 Dec 2007 21:18:57 -0700 [thread overview]
Message-ID: <m1prxhq0ni.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20071207161508.afe8fdf1.akpm@linux-foundation.org> (Andrew Morton's message of "Fri, 7 Dec 2007 16:15:08 -0800")
Andrew Morton <akpm@linux-foundation.org> writes:
> OK, perhaps a revert is the best thing to do here. I don't think anyone
> will be expecting fully finalised and robust netns support in 2.6.24.
I do think we expect /proc/net when the netns support is disabled
to be as robust as it has been prior to 2.6.24, which is where we came
in.
The problem I tried to close one hole too many with my previous patch.
The simplest thing to do and that will make things work for everyone
in a tried and true fashion is not a complete revert but to simply
remove d_revalidate (which is causing all of the trouble).
We can figure out how to deal with the VFS mount handling not being
friendly to network filesystems later. The implementation details of
VFS mount handling do not lest us remove dcache entries for
directories (even when they have been removed from the backing store)
until we have removed all mounts from them and their children. Since
I violated that rule. Kaboom!
Eric
next prev parent reply other threads:[~2007-12-08 4:21 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-07 4:45 2.6.24-rc3-git4 NFS crossmnt regression Shane
2007-12-07 12:02 ` Andrew Morton
2007-12-07 18:14 ` Shane
2007-12-07 18:36 ` Shane
2007-12-07 18:46 ` Trond Myklebust
2007-12-07 18:55 ` Shane
2007-12-07 19:16 ` Shane
2007-12-07 19:39 ` Shane
2007-12-07 22:51 ` Trond Myklebust
2007-12-07 23:14 ` Andrew Morton
2007-12-07 23:35 ` Eric W. Biederman
2007-12-07 23:43 ` Rafael J. Wysocki
2007-12-08 0:00 ` Alexey Dobriyan
2007-12-08 0:15 ` Andrew Morton
2007-12-08 2:13 ` Shane
2007-12-08 4:18 ` Eric W. Biederman [this message]
2007-12-08 4:25 ` [PATCH 2.6.24-rc4] proc: Remove/Fix proc generic d_revalidate Eric W. Biederman
2007-12-08 17:15 ` Shane
2007-12-10 2:52 ` Petr Vandrovec
2007-12-10 13:32 ` Denis V. Lunev
2007-12-10 19:35 ` Andrew Morton
2007-12-10 21:35 ` vandrove
2007-12-08 4:39 ` 2.6.24-rc3-git4 NFS crossmnt regression Eric W. Biederman
2007-12-09 0:20 ` Maxim Levitsky
2007-12-09 19:50 ` J. Bruce Fields
2007-12-10 5:03 ` Neil Brown
2007-12-10 14:19 ` Maxim Levitsky
2007-12-10 14:36 ` J. Bruce Fields
2007-12-10 15:05 ` Maxim Levitsky
2007-12-10 15:47 ` J. Bruce Fields
2007-12-10 18:22 ` Maxim Levitsky
2007-12-10 21:03 ` Andrew Morton
2007-12-12 2:01 ` 2.6.24-rc3-git4 NFS crossmnt regression [SOLVED] Maxim Levitsky
2007-12-12 2:15 ` Andrew Morton
2007-12-12 2:19 ` Trond Myklebust
2007-12-12 2:44 ` Andrew Morton
2007-12-12 2:24 ` Maxim Levitsky
2007-12-10 19:51 ` 2.6.24-rc3-git4 NFS crossmnt regression Shane
2007-12-07 22:33 ` Andrew Morton
2007-12-07 22:39 ` Trond Myklebust
2007-12-07 19:54 ` Rafael J. Wysocki
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=m1prxhq0ni.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bfields@fieldses.org \
--cc=den@openvz.org \
--cc=gnome42@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--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 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).