diff options
author | Christian Brauner <christian.brauner@ubuntu.com> | 2021-01-21 16:19:44 +0300 |
---|---|---|
committer | Christian Brauner <christian.brauner@ubuntu.com> | 2021-01-24 16:27:20 +0300 |
commit | 3cee6079f62f4d3a37d9dda2e0851677e08028ff (patch) | |
tree | d06df042d5feaadad59ccd3c53f7611740db0f3e /security/integrity/ima/ima_api.c | |
parent | 549c7297717c32ee53f156cd949e055e601f67bb (diff) | |
download | linux-3cee6079f62f4d3a37d9dda2e0851677e08028ff.tar.xz |
apparmor: handle idmapped mounts
The i_uid and i_gid are mostly used when logging for AppArmor. This is
broken in a bunch of places where the global root id is reported instead
of the i_uid or i_gid of the file. Nonetheless, be kind and log the
mapped inode if we're coming from an idmapped mount. If the initial user
namespace is passed nothing changes so non-idmapped mounts will see
identical behavior as before.
Link: https://lore.kernel.org/r/20210121131959.646623-26-christian.brauner@ubuntu.com
Signed-off-by: Christian Brauner <christian.brauner@ubuntu.com>
Diffstat (limited to 'security/integrity/ima/ima_api.c')
0 files changed, 0 insertions, 0 deletions