From: John Johansen <john.johansen@canonical.com>
To: Ben Dooks <ben.dooks@codethink.co.uk>, apparmor@lists.ubuntu.com
Cc: linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] apparmor: make stack_msg static
Date: Thu, 4 Jan 2024 01:42:30 -0800 [thread overview]
Message-ID: <5daba923-de64-41c1-8706-2b77939c5e3e@canonical.com> (raw)
In-Reply-To: <20231122115611.285625-1-ben.dooks@codethink.co.uk>
On 11/22/23 03:56, Ben Dooks wrote:
> The stack_msg is not exported out of security/apparmor/domain.c so
> make it static to avoid the following sparse warning:
>
> security/apparmor/domain.c:1314:12: warning: symbol 'stack_msg' was not declared. Should it be static?
>
> Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
thankyou for your contribution, unfortunately an the same patch went into apparmor-next on November 11
> ---
> security/apparmor/domain.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/security/apparmor/domain.c b/security/apparmor/domain.c
> index 89fbeab4b33b..571158ec6188 100644
> --- a/security/apparmor/domain.c
> +++ b/security/apparmor/domain.c
> @@ -1311,7 +1311,7 @@ static int change_profile_perms_wrapper(const char *op, const char *name,
> return error;
> }
>
> -const char *stack_msg = "change_profile unprivileged unconfined converted to stacking";
> +static const char *stack_msg = "change_profile unprivileged unconfined converted to stacking";
>
> /**
> * aa_change_profile - perform a one-way profile transition
prev parent reply other threads:[~2024-01-04 9:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 11:56 Ben Dooks
2024-01-04 9:42 ` 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=5daba923-de64-41c1-8706-2b77939c5e3e@canonical.com \
--to=john.johansen@canonical.com \
--cc=apparmor@lists.ubuntu.com \
--cc=ben.dooks@codethink.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.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®