From: John Johansen <john.johansen@canonical.com>
To: Mateusz Guzik <mjguzik@gmail.com>
Cc: paul@paul-moore.com, linux-kernel@vger.kernel.org,
apparmor@lists.ubuntu.com, linux-security-module@vger.kernel.org
Subject: Re: [PATCH] apparmor: use the condition in AA_BUG_FMT even with debug disabled
Date: Wed, 29 Jan 2025 03:46:41 -0800 [thread overview]
Message-ID: <7de8eeda-55bd-4104-88af-0a408d928935@canonical.com> (raw)
In-Reply-To: <20250127205404.3116679-1-mjguzik@gmail.com>
On 1/27/25 12:54, Mateusz Guzik wrote:
> This follows the established practice and fixes a build failure for me:
> security/apparmor/file.c: In function ‘__file_sock_perm’:
> security/apparmor/file.c:544:24: error: unused variable ‘sock’ [-Werror=unused-variable]
> 544 | struct socket *sock = (struct socket *) file->private_data;
> | ^~~~
>
> Signed-off-by: Mateusz Guzik <mjguzik@gmail.com>
Acked-by: John Johansen <john.johansen@canonical.com>
thanks, I have pulled this into my tree
> ---
>
> Plausibly the sock var wants to be eliminated altogether, but I just
> want this to build.
>
> security/apparmor/include/lib.h | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/security/apparmor/include/lib.h b/security/apparmor/include/lib.h
> index 256f4577c653..d947998262b2 100644
> --- a/security/apparmor/include/lib.h
> +++ b/security/apparmor/include/lib.h
> @@ -60,7 +60,11 @@ do { \
> #define AA_BUG_FMT(X, fmt, args...) \
> WARN((X), "AppArmor WARN %s: (" #X "): " fmt, __func__, ##args)
> #else
> -#define AA_BUG_FMT(X, fmt, args...) no_printk(fmt, ##args)
> +#define AA_BUG_FMT(X, fmt, args...) \
> + do { \
> + BUILD_BUG_ON_INVALID(X); \
> + no_printk(fmt, ##args); \
> + } while (0)
> #endif
>
> int aa_parse_debug_params(const char *str);
prev parent reply other threads:[~2025-01-29 11:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-27 20:54 Mateusz Guzik
2025-01-27 20:59 ` Ryan Lee
2025-01-27 21:07 ` Mateusz Guzik
2025-01-29 11:46 ` 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=7de8eeda-55bd-4104-88af-0a408d928935@canonical.com \
--to=john.johansen@canonical.com \
--cc=apparmor@lists.ubuntu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mjguzik@gmail.com \
--cc=paul@paul-moore.com \
/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®