From: ebiederm@xmission.com (Eric W. Biederman)
To: Richard Guy Briggs <rgb@redhat.com>
Cc: cgroups@vger.kernel.org,
Linux Containers <containers@lists.linux-foundation.org>,
Linux API <linux-api@vger.kernel.org>,
Linux Audit <linux-audit@redhat.com>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linux Network Development <netdev@vger.kernel.org>,
Simo Sorce <simo@redhat.com>, Carlos O'Donell <carlos@redhat.com>,
Aristeu Rozanski <arozansk@redhat.com>,
David Howells <dhowells@redhat.com>,
Eric Paris <eparis@parisplace.org>,
Daniel Walsh <dwalsh@redhat.com>,
jlayton@redhat.com, Andy Lutomirski <luto@kernel.org>,
mszeredi@redhat.com, Paul Moore <pmoore@redhat.com>,
"Serge E. Hallyn" <serge@hallyn.com>,
Steve Grubb <sgrubb@redhat.com>,
trondmy@primarydata.com, Al Viro <viro@zeniv.linux.org.uk>,
Madz Car <madzcar@gmail.com>
Subject: Re: RFC(V3): Audit Kernel Container IDs
Date: Tue, 09 Jan 2018 19:05:51 -0600 [thread overview]
Message-ID: <87k1wqcykw.fsf@xmission.com> (raw)
In-Reply-To: <20180109121620.wi7dq2423ugsraqv@madcap2.tricolour.ca> (Richard Guy Briggs's message of "Tue, 9 Jan 2018 07:16:20 -0500")
Please let's have a description of the problem you are trying to solve.
A proposed solution without talking about the problem space is useless.
Any proposed solution could potentially work.
I know to these exist. There is motivation for your work.
What is the motivation?
What problem are you trying to solve?
In particular what information are you trying to get into logs that you
can not get into the logs today?
I am going to try to give this the attention it deserves but right now I
am having to deal with half thought out patches for information leaks
from speculative code paths, so I won't be able to give this much
attention for a little bit.
Eric
next prev parent reply other threads:[~2018-01-10 1:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 12:16 RFC(V3): Audit Kernel Container IDs Richard Guy Briggs
2018-01-09 16:18 ` Simo Sorce
2018-01-10 7:00 ` Richard Guy Briggs
2018-02-02 21:24 ` Paul Moore
2018-02-02 22:19 ` Simo Sorce
2018-02-02 23:24 ` Paul Moore
2018-02-03 19:05 ` Casey Schaufler
2018-02-05 13:47 ` Simo Sorce
2018-02-02 21:18 ` Paul Moore
2018-01-10 1:05 ` Eric W. Biederman [this message]
2018-01-10 6:54 ` Richard Guy Briggs
2018-02-02 22:05 ` Paul Moore
2018-02-03 1:57 ` Serge E. Hallyn
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=87k1wqcykw.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=arozansk@redhat.com \
--cc=carlos@redhat.com \
--cc=cgroups@vger.kernel.org \
--cc=containers@lists.linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=dwalsh@redhat.com \
--cc=eparis@parisplace.org \
--cc=jlayton@redhat.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-audit@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=madzcar@gmail.com \
--cc=mszeredi@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pmoore@redhat.com \
--cc=rgb@redhat.com \
--cc=serge@hallyn.com \
--cc=sgrubb@redhat.com \
--cc=simo@redhat.com \
--cc=trondmy@primarydata.com \
--cc=viro@zeniv.linux.org.uk \
/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