From: ebiederm@xmission.com (Eric W. Biederman)
To: Dave Airlie <airlied@gmail.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-fsdevel@vger.kernel.org,
"Serge E. Hallyn" <serge@hallyn.com>,
David Miller <davem@davemloft.net>,
David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org
Subject: Re: [REVIEW][PATCH 12/15] userns: Convert drm to use kuid and kgid and struct pid where appropriate
Date: Wed, 12 Sep 2012 19:14:55 -0700 [thread overview]
Message-ID: <87ligefz34.fsf@xmission.com> (raw)
In-Reply-To: <CAPM=9ty=0=+w8VaFC9QhajUkYwmym_JaWR9sbwmgw5tCKg5nGw@mail.gmail.com> (Dave Airlie's message of "Thu, 13 Sep 2012 11:31:36 +1000")
Dave Airlie <airlied@gmail.com> writes:
>> Blink Blink this had not been converted to use struct pid ages ago?
>>
>> - On drm open capture the openers kuid and struct pid.
>> - On drm close release the kuid and struct pid
>> - When reporting the uid and pid convert the kuid and struct pid
>> into values in the appropriate namespace.
>>
>
> Hi Eric,
>
> I'm fine with this seems okay, do you want me to merge it via
> drm-next?
My plan is to merge it via my user namespace tree. And since you have
responed positively I will add your acked-by. There are some nice
synergies when I get all of the changes in one tree.
If for some reason you want to carry this in your drm tree we can work
something out.
In this case I expect the change isn't big enough to worry about.
Eric
next prev parent reply other threads:[~2012-09-13 2:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87lih2h6i4.fsf@xmission.com>
2012-08-26 0:05 ` [REVIEW][PATCH 12/15] userns: Convert drm to use kuid and kgid and struct pid where appropriate Eric W. Biederman
2012-09-13 1:31 ` Dave Airlie
2012-09-13 2:14 ` Eric W. Biederman [this message]
2012-09-13 3:29 ` Dave Airlie
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=87ligefz34.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=airlied@gmail.com \
--cc=airlied@linux.ie \
--cc=davem@davemloft.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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