From: Oleg Nesterov <oleg@redhat.com>
To: Georgia Garcia <georgia.garcia@canonical.com>
Cc: Bradley Morgan <include@grrlz.net>,
apparmor@lists.ubuntu.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: Wed, 8 Jul 2026 16:14:23 +0200 [thread overview]
Message-ID: <ak5bP11v3hbWQ9Yw@redhat.com> (raw)
In-Reply-To: <9f37884fc0922254c3d3708794cf1272f4fabdfc.camel@canonical.com>
On 07/08, Georgia Garcia wrote:
>
> On Sun, 2026-07-05 at 20:48 +0200, Oleg Nesterov wrote:
> > 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.
> >
>
> Yes, I agree. Perhaps SEND_SIG_PRIV would be more appropriate here.
Yes, this is what I meant. And I think the same is true for most of (all?)
users of send_sig(sig, task, priv = 0), at least when task is current.
I'll return to this later.
Thanks for your ACK!
Oleg.
next prev parent reply other threads:[~2026-07-08 14:14 UTC|newest]
Thread overview: 8+ 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 [this message]
2026-07-08 14:23 ` Bradley Morgan
2026-07-08 14:03 ` Georgia Garcia
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=ak5bP11v3hbWQ9Yw@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome