From: Georgia Garcia <georgia.garcia@canonical.com>
To: Oleg Nesterov <oleg@redhat.com>,
John Johansen <john.johansen@canonical.com>,
Paul Moore <paul@paul-moore.com>,
James Morris <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>
Cc: apparmor@lists.ubuntu.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] apparmor: use SEND_SIG_NOINFO instead of NULL in aa_audit()
Date: Wed, 08 Jul 2026 11:03:08 -0300 [thread overview]
Message-ID: <f3d7e5567bfbbca959f561f58cb9003b1868186c.camel@canonical.com> (raw)
In-Reply-To: <akqL3YWi28ZUzca3@redhat.com>
Hi Oleg,
On Sun, 2026-07-05 at 18:52 +0200, Oleg Nesterov wrote:
> SEND_SIG_NOINFO is defined as ((struct kernel_siginfo *) 0), so passing
> NULL works, but:
>
> - this works "by accident" and looks as if the caller doesn't understand
> the signal sending API.
>
> - more importantly, this hides the usage of SEND_SIG_NOINFO from grep,
> and this is really bad.
>
Acked-by: Georgia Garcia <georgia.garcia@canonical.com>
> Signed-off-by: Oleg Nesterov <oleg@redhat.com>
> ---
> security/apparmor/audit.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/security/apparmor/audit.c b/security/apparmor/audit.c
> index 4a60b6fda75f..15e42e96b163 100644
> --- a/security/apparmor/audit.c
> +++ b/security/apparmor/audit.c
> @@ -192,7 +192,7 @@ int aa_audit(int type, struct aa_profile *profile,
> aa_audit_msg(type, ad, cb);
>
> if (ad->type == AUDIT_APPARMOR_KILL)
> - (void)send_sig_info(profile->signal, NULL,
> + send_sig_info(profile->signal, SEND_SIG_NOINFO,
> ad->common.type == LSM_AUDIT_DATA_TASK &&
> ad->common.u.tsk ? ad->common.u.tsk : current);
>
next prev parent reply other threads:[~2026-07-08 14:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-05 16:52 Oleg Nesterov
2026-07-05 17:53 ` Bradley Morgan
2026-07-05 18:48 ` Oleg Nesterov
2026-07-05 18:52 ` Bradley Morgan
2026-07-08 14:05 ` Georgia Garcia
2026-07-08 14:14 ` Oleg Nesterov
2026-07-08 14:23 ` Bradley Morgan
2026-07-08 14:03 ` Georgia Garcia [this message]
2026-08-06 7:23 ` John Johansen
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=f3d7e5567bfbbca959f561f58cb9003b1868186c.camel@canonical.com \
--to=georgia.garcia@canonical.com \
--cc=apparmor@lists.ubuntu.com \
--cc=jmorris@namei.org \
--cc=john.johansen@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.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®