diff options
| author | Eric Paris <eparis@redhat.com> | 2010-07-23 11:43:51 -0400 |
|---|---|---|
| committer | James Morris <jmorris@namei.org> | 2010-08-02 15:35:06 +1000 |
| commit | 9cfcac810e8993fa7a5bfd24b1a21f1dbbb03a7b (patch) | |
| tree | 86fae80c744e46b15b8eb9aa23fead7e63a64159 /security/smack/smack_lsm.c | |
| parent | 692a8a231b212dfc68f612956d63f34abf098e0f (diff) | |
| download | linux-9cfcac810e8993fa7a5bfd24b1a21f1dbbb03a7b.tar.gz linux-9cfcac810e8993fa7a5bfd24b1a21f1dbbb03a7b.tar.bz2 linux-9cfcac810e8993fa7a5bfd24b1a21f1dbbb03a7b.zip | |
vfs: re-introduce MAY_CHDIR
Currently MAY_ACCESS means that filesystems must check the permissions
right then and not rely on cached results or the results of future
operations on the object. This can be because of a call to sys_access() or
because of a call to chdir() which needs to check search without relying on
any future operations inside that dir. I plan to use MAY_ACCESS for other
purposes in the security system, so I split the MAY_ACCESS and the
MAY_CHDIR cases.
Signed-off-by: Eric Paris <eparis@redhat.com>
Acked-by: Stephen D. Smalley <sds@tycho.nsa.gov>
Signed-off-by: James Morris <jmorris@namei.org>
Diffstat (limited to 'security/smack/smack_lsm.c')
0 files changed, 0 insertions, 0 deletions