linux-kernel - Re: [PATCH -V19 00/15] Generic name to handle and open by handle syscalls

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: <E1Ov3wR-0000Ua-LC@pomaz-ex.szeredi.hu>
Date:	Mon, 13 Sep 2010 09:59:07 +0200
From:	Miklos Szeredi <miklos@...redi.hu>
To:	Neil Brown <neilb@...e.de>
CC:	miklos@...redi.hu, aneesh.kumar@...ux.vnet.ibm.com,
	hch@...radead.org, viro@...iv.linux.org.uk, adilger@....com,
	corbet@....net, npiggin@...nel.dk, hooanon05@...oo.co.jp,
	bfields@...ldses.org, linux-fsdevel@...r.kernel.org,
	sfrench@...ibm.com, philippe.deniel@....FR,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH -V19 00/15] Generic name to handle and open by handle
 syscalls

On Mon, 13 Sep 2010, Neil Brown wrote:
> > You can implement ->read() on the symlink file instead.
> 
> I would suggest that is a much uglier hack than changed readlinkat to accept
> a NULL pathname.

I think read(2) is a natural interface for reading symlinks and would
have been a perfectly fine API to choose instead of a specialized
syscall.

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/