From: Steve Grubb <sgrubb@redhat.com>
To: "Roberts, William C" <william.c.roberts@intel.com>
Cc: "seandroid-list@tycho.nsa.gov" <seandroid-list@tycho.nsa.gov>,
"selinux@tycho.nsa.gov" <selinux@tycho.nsa.gov>,
"linux-audit@redhat.com" <linux-audit@redhat.com>
Subject: Re: [PATCH] selinux: print leading 0x on ioctlcmd audits
Date: Fri, 15 Jul 2016 15:41:37 -0400 [thread overview]
Message-ID: <3333447.I3SejC0nv6@x2> (raw)
In-Reply-To: <476DC76E7D1DF2438D32BFADF679FC56012585BF@ORSMSX103.amr.corp.intel.com>
On Friday, July 15, 2016 7:33:09 PM EDT Roberts, William C wrote:
> <snip>
>
> > > This is important so that people don't make up new ones that do the
> > > same thing. The ioctlcmd field name should be recorded. Are there more
> > > that need documenting?
> >
> > Steve/William, one of you want to send a patch/PR for the field
> > dictionary?
>
> I'll send it over.
I also asked some other questions. Is this the ioctl number? As in syscall
arg a1? I need to know if its the same thing so that I can hook up its
translation if so.
Thanks,
-Steve
WARNING: multiple messages have this Message-ID (diff)
From: Steve Grubb <sgrubb@redhat.com>
To: "Roberts, William C" <william.c.roberts@intel.com>
Cc: Paul Moore <pmoore@redhat.com>,
William Roberts <bill.c.roberts@gmail.com>,
"seandroid-list@tycho.nsa.gov" <seandroid-list@tycho.nsa.gov>,
"selinux@tycho.nsa.gov" <selinux@tycho.nsa.gov>,
"linux-audit@redhat.com" <linux-audit@redhat.com>
Subject: Re: [PATCH] selinux: print leading 0x on ioctlcmd audits
Date: Fri, 15 Jul 2016 15:41:37 -0400 [thread overview]
Message-ID: <3333447.I3SejC0nv6@x2> (raw)
In-Reply-To: <476DC76E7D1DF2438D32BFADF679FC56012585BF@ORSMSX103.amr.corp.intel.com>
On Friday, July 15, 2016 7:33:09 PM EDT Roberts, William C wrote:
> <snip>
>
> > > This is important so that people don't make up new ones that do the
> > > same thing. The ioctlcmd field name should be recorded. Are there more
> > > that need documenting?
> >
> > Steve/William, one of you want to send a patch/PR for the field
> > dictionary?
>
> I'll send it over.
I also asked some other questions. Is this the ioctl number? As in syscall
arg a1? I need to know if its the same thing so that I can hook up its
translation if so.
Thanks,
-Steve
next prev parent reply other threads:[~2016-07-15 19:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-14 19:29 [PATCH] selinux: print leading 0x on ioctlcmd audits william.c.roberts
2016-07-14 22:17 ` Paul Moore
2016-07-14 22:17 ` Paul Moore
2016-07-14 23:18 ` William Roberts
2016-07-14 23:18 ` William Roberts
2016-07-14 23:33 ` William Roberts
2016-07-14 23:33 ` William Roberts
2016-07-15 18:19 ` Paul Moore
2016-07-15 18:19 ` Paul Moore
2016-07-15 18:54 ` Steve Grubb
2016-07-15 18:54 ` Steve Grubb
2016-07-15 19:02 ` Paul Moore
2016-07-15 19:02 ` Paul Moore
2016-07-15 19:33 ` Roberts, William C
2016-07-15 19:41 ` Steve Grubb [this message]
2016-07-15 19:41 ` Steve Grubb
2016-07-15 19:49 ` Roberts, William C
2016-07-15 19:49 ` Roberts, William C
2016-07-15 20:12 ` Steve Grubb
2016-07-15 20:12 ` Steve Grubb
2016-07-15 19:31 ` Roberts, William C
2016-07-15 19:31 ` Roberts, William C
[not found] ` <476DC76E7D1DF2438D32BFADF679FC56012585A7-P5GAC/sN6hlQxe9IK+vIArfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2016-07-15 19:35 ` Paul Moore
2016-07-15 19:35 ` Paul Moore
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=3333447.I3SejC0nv6@x2 \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.com \
--cc=seandroid-list@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=william.c.roberts@intel.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.