| 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
| ||
|
Date: Tue, 8 Jul 2014 13:48:27 +0100 From: Meredydd Luff <meredydd@...atehouse.org> To: Christoph Hellwig <hch@...radead.org> Cc: Andy Lutomirski <luto@...capital.net>, David Drysdale <drysdale@...gle.com>, Al Viro <viro@...iv.linux.org.uk>, LSM List <linux-security-module@...r.kernel.org>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, James Morris <james.l.morris@...cle.com>, Kees Cook <keescook@...omium.org>, Linux API <linux-api@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, linux-man@...r.kernel.org Subject: Re: [PATCH 01/11] fs: add O_BENEATH_ONLY flag to openat(2) On 8 July 2014 13:07, Christoph Hellwig <hch@...radead.org> wrote: > There's two different AT_* namespaces. The flags that most *at syscalls > has, and the the one for the dfd argument, which currently only contains > AT_FDCWD, although a new constant has recently been proposed to it. > > Having an AT_BENEATH magic value for the dfd argument certainly feels > elegant to me How would that work? The directory beneath which openat is looking is conveyed in the dfd argument itself. If I'm understanding this right, you'd have to pass a different value for "open relative to fd#5" and "open relative to fd#5, but beneath it only", which doesn't sound hugely elegant to me. Meredydd -- 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/
Powered by blists - more mailing lists