From: Pavel Machek <pavel@ucw.cz>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: jlayton@redhat.com, ebiederm@xmission.com,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] procfs: make /proc style symlinks behave like "normal" symlinks
Date: Fri, 20 Nov 2009 10:51:29 +0100 [thread overview]
Message-ID: <20091120095129.GD11212@elf.ucw.cz> (raw)
In-Reply-To: <E1NBPq8-0001D7-F9@pomaz-ex.szeredi.hu>
On Fri 2009-11-20 10:31:40, Miklos Szeredi wrote:
> On Thu, 19 Nov 2009, Pavel Machek wrote:
> > > 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.
>
> What is this "Pavel's issue"?
The one we were talking about, see bugtraq.
> > One posibility would be to make open(/proc/XX/fd/XX) behave like
> > dup(). That should solve the NFS problems, too, no?
>
> You mean, reuse the old "struct file" for the new open? Or what?
Aha, dup() results in file position being shared. You are right,
that's not going to fly :-(.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2009-11-20 9:51 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
2009-11-20 9:31 ` Miklos Szeredi
2009-11-20 9:51 ` Pavel Machek [this message]
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=20091120095129.GD11212@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 \
--cc=miklos@szeredi.hu \
/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.