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: Sun, 20 Sep 2009 18:52:01 -0700 From: Nicholas Miell <nmiell@...cast.net> To: Eric Paris <eparis@...hat.com> Cc: linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org, viro@...iv.linux.org.uk, hch@...radead.org Subject: Re: [PATCH] VFS: document what MAY_ACCESS means Since this is a documentation patch, here are some nits. > +/* > + * The vfs MAY_ACCESS flag really means that we might not use the object > + * immediately (consider chdir which might not actually use the new dir). > + * Thus permissions must be checked mmediately rather than relying on later ^ immediately > + * checks during the actual user of the object in question. This is an ^ use > + * internal flag and should not come from userspace. > + */ > #define MAY_ACCESS 16 > #define MAY_OPEN 32 -- Nicholas Miell <nmiell@...cast.net> -- 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