From: Stefano Brivio <sbrivio@redhat.com>
To: "Maxime Bélair" <maxime.belair@canonical.com>
Cc: passt-dev@passt.top
Subject: Re: [PATCH] apparmor: Fix passt abstraction
Date: Fri, 17 May 2024 14:28:09 +0200 [thread overview]
Message-ID: <20240517142809.265e69f3@elisabeth> (raw)
In-Reply-To: <20240517115053.53072-1-maxime.belair@canonical.com>
Hi Maxime,
On Fri, 17 May 2024 13:50:54 +0200
Maxime Bélair <maxime.belair@canonical.com> wrote:
> Commit b686afa2 introduced the invalid apparmor rule `mount options=(rw, runbindable) /,` since runbindable mount rules cannot have a source.
Oops, right, I didn't actually drop the source specification there. :(
Thanks for fixing this.
> Therefore running aa-logprof/aa-genprof will trigger errors (see https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2065685)
>
> $ sudo aa-logprof
> ERROR: Operation {'runbindable'} cannot have a source. Source = AARE('/')
I wonder why I don't see this on Debian testing with AppArmor 3.0.13
(same on openSUSE Tumbleweed).
Is there something in particular I should do to reproduce/check this?
> This patch fixes it to the intended behavior.
>
> Signed-off-by: Maxime Bélair <maxime.belair@canonical.com>
> ---
> contrib/apparmor/abstractions/passt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/contrib/apparmor/abstractions/passt b/contrib/apparmor/abstractions/passt
> index 61ec32c..d245115 100644
> --- a/contrib/apparmor/abstractions/passt
> +++ b/contrib/apparmor/abstractions/passt
> @@ -26,7 +26,7 @@
> capability sys_ptrace,
>
> / r, # isolate_prefork(), isolation.c
> - mount options=(rw, runbindable) /,
> + mount options=(rw, runbindable) -> /,
> mount "" -> "/",
> mount "" -> "/tmp/",
> pivot_root "/tmp/" -> "/tmp/",
--
Stefano
next prev parent reply other threads:[~2024-05-17 12:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-17 11:50 [PATCH] apparmor: Fix passt abstraction Maxime Bélair
2024-05-17 12:28 ` Stefano Brivio [this message]
2024-05-21 7:50 ` Maxime Bélair
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=20240517142809.265e69f3@elisabeth \
--to=sbrivio@redhat.com \
--cc=maxime.belair@canonical.com \
--cc=passt-dev@passt.top \
/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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for IMAP folder(s).