From: John Johansen <john.johansen@canonical.com>
To: Alexander Mikhalitsyn <aleksandr.mikhalitsyn@canonical.com>
Cc: stgraber@stgraber.org, brauner@kernel.org,
apparmor@lists.ubuntu.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] apparmor: take nosymfollow flag into account
Date: Sat, 9 Nov 2024 14:16:17 -0800 [thread overview]
Message-ID: <95fb73d2-4d29-41d9-be52-48c5d58d43e0@canonical.com> (raw)
In-Reply-To: <20240628153712.288166-1-aleksandr.mikhalitsyn@canonical.com>
On 6/28/24 08:37, Alexander Mikhalitsyn wrote:
> 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>
As I am trying to sort through the back log I found that
some how my reply to this got dropped. So just to document
on list, this landed in 6.11
> ---
> security/apparmor/mount.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/security/apparmor/mount.c b/security/apparmor/mount.c
> index 49fe8da6fea4..bf8863253e07 100644
> --- 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)
prev parent reply other threads:[~2024-11-09 22:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 15:37 Alexander Mikhalitsyn
2024-07-15 14:19 ` [apparmor] " Georgia Garcia
2024-11-09 22:16 ` John Johansen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=95fb73d2-4d29-41d9-be52-48c5d58d43e0@canonical.com \
--to=john.johansen@canonical.com \
--cc=aleksandr.mikhalitsyn@canonical.com \
--cc=apparmor@lists.ubuntu.com \
--cc=brauner@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stgraber@stgraber.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®