From: Pavel Machek <pavel@ucw.cz>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Jeff Layton <jlayton@redhat.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] procfs: make /proc style symlinks behave like "normal" symlinks
Date: Thu, 19 Nov 2009 23:30:18 +0100 [thread overview]
Message-ID: <20091119223018.GC11212@elf.ucw.cz> (raw)
In-Reply-To: <m1vdh6uqjn.fsf@fess.ebiederm.org>
Hi!
(Sorry, missed Cc's first time).
> >> Adding the missing revalidations is fine, but I don't believe that
> >> helps to fix Pavel's issue. I'll go back and take a more careful look
> >> at the suggestion that Miklos made and see whether it makes sense to
> >> implement a new FS_* flag for this, and see what it'll take to fix
> >> Pavel's issue.
> >
> > One posibility would be to make open(/proc/XX/fd/XX) behave like
> > dup(). That should solve the NFS problems, too, no?
>
> Not for bind mounts, and the revalidate in follow_mounts is a bug regardless.
Really? So dup() is also broken on nfs? How do bind mounts affect
dup()?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2009-11-19 22:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-19 13:44 [PATCH] procfs: make /proc style symlinks behave like "normal" symlinks Jeff Layton
2009-11-19 17:07 ` Eric W. Biederman
2009-11-19 18:28 ` Jeff Layton
2009-11-19 18:57 ` Eric W. Biederman
2009-11-19 19:35 ` Jeff Layton
2009-11-19 21:31 ` Eric W. Biederman
2009-11-19 21:39 ` Pavel Machek
2009-11-19 21:56 ` Eric W. Biederman
2009-11-19 22:30 ` Pavel Machek [this message]
2009-11-20 9:31 ` Miklos Szeredi
2009-11-20 9:51 ` Pavel Machek
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=20091119223018.GC11212@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=ebiederm@xmission.com \
--cc=jlayton@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).