linux-kernel - Re: [PATCH -V18 04/13] vfs: Allow handle based open on 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]

Date:	Fri, 20 Aug 2010 19:53:03 +1000
From:	Neil Brown <neilb@...e.de>
To:	Christoph Hellwig <hch@...radead.org>
Cc:	"Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>,
	viro@...iv.linux.org.uk, adilger@....com, corbet@....net,
	npiggin@...e.de, hooanon05@...oo.co.jp, bfields@...ldses.org,
	miklos@...redi.hu, linux-fsdevel@...r.kernel.org,
	sfrench@...ibm.com, philippe.deniel@....FR,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH -V18 04/13] vfs: Allow handle based open on symlinks

On Fri, 20 Aug 2010 04:30:57 -0400
Christoph Hellwig <hch@...radead.org> wrote:

> Suddenly getting an file pointer for a symlink which could never happen
> before is a really bad idea.  Just add a proper readlink_by_handle
> system call, similar to what's done in the XFS interface.

Why is that?
With futexes we suddenly get a file descriptor for something we could never
get a file descriptor on before and that doesn't seem to be a problem.

Why should symlinks be special as the only thing that you cannot have a file
descriptor for?  Uniformity of interface is a very valuable property.

NeilBrown
--
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/