linux-kernel - Re: [PATCH] procfs: make /proc style symlinks behave like "normal" symlinks

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <E1NBPq8-0001D7-F9@pomaz-ex.szeredi.hu>
Date:	Fri, 20 Nov 2009 10:31:40 +0100
From:	Miklos Szeredi <miklos@...redi.hu>
To:	Pavel Machek <pavel@....cz>
CC:	jlayton@...hat.com, ebiederm@...ssion.com,
	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH] procfs: make /proc style symlinks behave like "normal"
 symlinks

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"?

> 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?

Thanks,
Miklos
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/