From: Steve Grubb <sgrubb@redhat.com>
To: Paul Moore <pmoore@redhat.com>
Cc: Richard Guy Briggs <rgb@redhat.com>, linux-audit@redhat.com
Subject: Re: [userspace PATCH v2 0/2] Add support for loginuid_set
Date: Mon, 17 Oct 2016 18:21:31 -0400 [thread overview]
Message-ID: <1594202.aPB8anKs2i@x2> (raw)
In-Reply-To: <CAGH-KgsMSbsD9j0Buyipzzbh1v-M36k8iQ1o+WkL8iiQwA66xQ@mail.gmail.com>
On Monday, October 17, 2016 5:19:59 PM EDT Paul Moore wrote:
> We haven't merged any of the session ID code into the kernel so
> changes are still possible. The logic for supporting loginuid_set
> (UID namespace issues) don't really apply to session IDs so I think we
> can drop the sessionid_set part of the API and just use the -1
> sentinel.
OK, that's good to hear. I'll fix up and merge the sessionid patch - no need to
re-send the user space piece.
-Steve
next prev parent reply other threads:[~2016-10-17 22:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 18:18 [userspace PATCH v2 0/2] Add support for loginuid_set Richard Guy Briggs
2016-08-18 18:18 ` [userspace PATCH v2 1/2] get feature list only once Richard Guy Briggs
2016-08-18 18:18 ` [userspace PATCH v2 2/2] Add user filter option loginuid_set from uapi macro AUDIT_LOGINUID_SET Richard Guy Briggs
2016-10-10 17:24 ` [userspace PATCH v2 0/2] Add support for loginuid_set Steve Grubb
2016-10-10 21:10 ` Paul Moore
2016-10-11 16:40 ` Steve Grubb
2016-10-11 18:27 ` Richard Guy Briggs
2016-10-11 19:22 ` Steve Grubb
2016-10-11 20:42 ` Paul Moore
2016-10-11 20:50 ` Steve Grubb
2016-10-11 20:54 ` Paul Moore
2016-10-11 21:31 ` Steve Grubb
2016-10-11 22:15 ` Paul Moore
2016-10-17 15:40 ` Richard Guy Briggs
2016-10-17 16:04 ` Steve Grubb
2016-10-17 16:51 ` Richard Guy Briggs
2016-10-17 17:06 ` Steve Grubb
2016-10-17 21:19 ` Paul Moore
2016-10-17 22:21 ` Steve Grubb [this message]
2016-10-18 4:35 ` Richard Guy Briggs
2016-10-18 10:48 ` Richard Guy Briggs
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=1594202.aPB8anKs2i@x2 \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.com \
--cc=pmoore@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 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.