From: Eric Paris <eparis@redhat.com>
To: Richard Guy Briggs <rgb@redhat.com>
Cc: linux-audit@redhat.com
Subject: Re: Is zero a valid value for the pid member of the AUDIT_SIGNAL_INFO message?
Date: Wed, 12 Mar 2014 14:27:13 -0400 [thread overview]
Message-ID: <1394648833.31201.3.camel@flatline.rdu.redhat.com> (raw)
In-Reply-To: <20140312182115.GA27244@madcap2.tricolour.ca>
On Wed, 2014-03-12 at 14:21 -0400, Richard Guy Briggs wrote:
> On 14/03/12, Eric Paris wrote:
> > On Wed, 2014-03-12 at 08:22 -0400, Steve Grubb wrote:
> > > On Tuesday, March 11, 2014 06:15:17 PM Richard Guy Briggs wrote:
> > > > Is zero a valid value for the pid member of the AUDIT_SIGNAL_INFO message?
> > >
> > > Well, pid=0 would be the kernel. So, its valid but unlikely.
> >
> > Actually, signals from the kernel will never get recorded here...
> >
> > > Offhand I don't
> > > know why the kernel might try sending a signal. Is this a problem?
> >
> > He's trying to figure out how to store this info in light of pid
> > namespaces. right now, auditd can only live in the initial pid
> > namespace, so can only get signals from processes in the initial pid
> > namespace, so we can store it as a number always in the initial pid
> > namespace. But if auditd were ever to not be in the initial pid
> > namespace, not sure what to do....
>
> Nice word column alignment above there Eric... ;-)
>
> I would be inclined to always store it in the initial pid namespace and
> then make a decision if it translates sanely when needed to the auditd
> namespace(s).
since for now auditd pid_ns == init pid_ns that's fine.
prev parent reply other threads:[~2014-03-12 18:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-11 22:15 Is zero a valid value for the pid member of the AUDIT_SIGNAL_INFO message? Richard Guy Briggs
2014-03-12 1:06 ` Eric Paris
2014-03-12 3:32 ` Richard Guy Briggs
2014-03-12 12:44 ` Steve Grubb
2014-03-12 15:35 ` Richard Guy Briggs
2014-03-12 16:07 ` Steve Grubb
2014-03-12 16:28 ` Richard Guy Briggs
2014-03-12 12:22 ` Steve Grubb
2014-03-12 15:28 ` Richard Guy Briggs
2014-03-12 16:35 ` Eric Paris
2014-03-12 18:21 ` Richard Guy Briggs
2014-03-12 18:27 ` Eric Paris [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=1394648833.31201.3.camel@flatline.rdu.redhat.com \
--to=eparis@redhat.com \
--cc=linux-audit@redhat.com \
--cc=rgb@redhat.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