apparmor: take nosymfollow flag into account

A "nosymfollow" flag was added in commit
dab741e0e02b ("Add a "nosymfollow" mount option.")

While we don't need to implement any special logic on
the AppArmor kernel side to handle it, we should provide
user with a correct list of mount flags in audit logs.

Signed-off-by: Alexander Mikhalitsyn <aleksandr.mikhalitsyn@canonical.com>
Reviewed-by: Georgia Garcia <georgia.garcia@canonical.com>
Signed-off-by: John Johansen <john.johansen@canonical.com>

diff --git a/security/apparmor/mount.c b/security/apparmor/mount.c
index 49fe8da6fea4597399f1b2113f230353a8b8c674..bf8863253e07226731c059a407a06a041909c1db 100644 (file)
--- a/security/apparmor/mount.c
+++ b/security/apparmor/mount.c
@@ -44,6 +44,8 @@ static void audit_mnt_flags(struct audit_buffer *ab, unsigned long flags)
                audit_log_format(ab, ", mand");
        if (flags & MS_DIRSYNC)
                audit_log_format(ab, ", dirsync");
+       if (flags & MS_NOSYMFOLLOW)
+               audit_log_format(ab, ", nosymfollow");
        if (flags & MS_NOATIME)
                audit_log_format(ab, ", noatime");
        if (flags & MS_NODIRATIME)