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: <E1OswT5-000709-U9@pomaz-ex.szeredi.hu>
Date:	Tue, 07 Sep 2010 13:36:03 +0200
From:	Miklos Szeredi <miklos@...redi.hu>
To:	"Aneesh Kumar K. V" <aneesh.kumar@...ux.vnet.ibm.com>
CC:	hch@...radead.org, viro@...iv.linux.org.uk, adilger@....com,
	corbet@....net, neilb@...e.de, npiggin@...nel.dk,
	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 -V19 00/15] Generic name to handle and open by handle syscalls

On Tue, 07 Sep 2010, Aneesh Kumar K. V wrote:
> Any update on this. Are you ok with syscall approach which is limitted to
> CAP_DAC_READ_SEARCH  ?

My gut reaction is: "not another bunch of xattr syscalls!".  It
doesn't feel right, this interface is too specialized to warrant a
full set of filesystem syscalls.

Al Viro is right that there are problems with symlinks.  What we
really want here is a sort of symlink that doesn't get followed.  One
way to provide that is to create a kernel internal "handle" filesystem
and direct open_by_handle() to that for anything not a directory or a
regular file.

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/