[apparmor] [PATCH 0/6] Use openat(2) style dirfd/path in new APIs
Tyler Hicks
tyhicks at canonical.com
Thu Mar 26 21:47:56 UTC 2015
This patch set modifies the new API functions to use the openat(2) style of a
dirfd and path for specifying a file.
The major downside of the patch set is that it may weaken the usefulness of
logging since path may be a single component. However, that can be addresses in
a future patch where the path of the dirfd can be determined by reading the
target of /proc/self/fd/%d, if desired.
Even if we don't move the new APIs over to the openat(2) style, I think that
the first 3 patches in the patch set are valid cleanups which simplify the code
are are worth merging either way.
Tyler
More information about the AppArmor
mailing list