From: Oleg Nesterov <oleg@redhat.com>
To: Bradley Morgan <include@grrlz.net>
Cc: apparmor@lists.ubuntu.com, georgia.garcia@canonical.com,
jmorris@namei.org, john.johansen@canonical.com,
linux-kernel@vger.kernel.org, paul@paul-moore.com,
serge@hallyn.com
Subject: Re: [PATCH] apparmor: use SEND_SIG_NOINFO instead of NULL in aa_audit()
Date: Sun, 5 Jul 2026 20:48:04 +0200 [thread overview]
Message-ID: <akqm5EMVZpqM6gnQ@redhat.com> (raw)
In-Reply-To: <65E9B858-C580-41A3-9B39-B383ED5F0ACF@grrlz.net>
On 07/05, Bradley Morgan 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.
> - also drop the now redundant (void)
Yes, but the "void" cast was never necessary, I guess.
and just in case... To me the usage of SEND_SIG_NOINFO here doesn't look right with
or without this change. Perhaps I am wrong, but please lets not discuss this right
now, this connects to other cleanups I have in mind.
The purpose of this change is to make aa_audit() grep-friendly wrt SEND_SIG_NOINFO.
And because send_sig_info(NULL) looks "just wrong" to me, no matter what.
> Reviewed-by: Bradley Morgan <include@grrlz.net>
Thanks,
> Also, feel free to CC me in signal patches, so I can review, from you
> or from others.
OK, will do.
Oleg.
next prev parent reply other threads:[~2026-07-05 18:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-05 16:52 [PATCH] apparmor: use SEND_SIG_NOINFO instead of NULL in aa_audit() Oleg Nesterov
2026-07-05 17:53 ` Bradley Morgan
2026-07-05 18:48 ` Oleg Nesterov [this message]
2026-07-05 18:52 ` Bradley Morgan
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=akqm5EMVZpqM6gnQ@redhat.com \
--to=oleg@redhat.com \
--cc=apparmor@lists.ubuntu.com \
--cc=georgia.garcia@canonical.com \
--cc=include@grrlz.net \
--cc=jmorris@namei.org \
--cc=john.johansen@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.