Searched hist:"9 cfcac810e8993fa7a5bfd24b1a21f1dbbb03a7b" (Results 1 – 4 of 4) sorted by relevance
| /openbmc/linux/fs/fuse/ |
| H A D | dir.c | diff 9cfcac810e8993fa7a5bfd24b1a21f1dbbb03a7b Fri Jul 23 10:43:51 CDT 2010 Eric Paris <eparis@redhat.com> 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>
|
| /openbmc/linux/fs/ |
| H A D | open.c | diff 9cfcac810e8993fa7a5bfd24b1a21f1dbbb03a7b Fri Jul 23 10:43:51 CDT 2010 Eric Paris <eparis@redhat.com> 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>
|
| /openbmc/linux/fs/nfs/ |
| H A D | dir.c | diff 9cfcac810e8993fa7a5bfd24b1a21f1dbbb03a7b Fri Jul 23 10:43:51 CDT 2010 Eric Paris <eparis@redhat.com> 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>
|
| /openbmc/linux/include/linux/ |
| H A D | fs.h | diff 9cfcac810e8993fa7a5bfd24b1a21f1dbbb03a7b Fri Jul 23 10:43:51 CDT 2010 Eric Paris <eparis@redhat.com> 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>
|