From: ebiederm@xmission.com (Eric W. Biederman)
To: Greg KH <greg@kroah.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org,
Linux Containers <containers@lists.osdl.org>,
linux-usb-devel@lists.sourceforge.net,
Greg Kroah-Hartman <gregkh@suse.de>
Subject: Re: [PATCH] usb: Fixup usb so it uses struct pid
Date: Sun, 10 Sep 2006 17:58:33 -0600 [thread overview]
Message-ID: <m1fyezclzq.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20060910213746.GA9565@kroah.com> (Greg KH's message of "Sun, 10 Sep 2006 14:37:46 -0700")
Greg KH <greg@kroah.com> writes:
> On Sat, Sep 09, 2006 at 10:42:10PM -0600, Eric W. Biederman wrote:
>>
>> The problem by remember a user space process by it's pid it is
>> possible that the process will exit, pid wrap around will occur and a
>> different process will appear in it's place. Holding a reference
>> to a struct pid avoid that problem, and paves the way
>> for implementing a pid namespace.
>>
>> Also since usb is the only user of kill_proc_info_as_uid
>> rename kill_proc_info_as_uid to kill_pid_info_as_uid
>> and have the new version take a struct pid.
>>
>> This patch is against 2.6.18-rc6-mm1.
>>
>> Signed-off-by: Eric W. Biederman <ebiederm@xmission.com>
>
> Looks good to me.
>
> Do you want me to take this in my tree, or will you be going through
> Andrew, like your other, related pid stuff? If through Andrew, please
> feel free to add:
> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Sure. I think going through Andrew makes sense. As I probably have
a helper function or two in Andrews tree that hasn't hit wider distribution.
Eric
prev parent reply other threads:[~2006-09-10 23:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-10 4:42 Eric W. Biederman
2006-09-10 18:12 ` Pete Zaitcev
2006-09-10 20:04 ` Eric W. Biederman
2006-09-12 14:52 ` [Devel] " Kirill Korotaev
2006-09-11 14:02 ` Herbert Poetzl
2006-09-10 21:37 ` Greg KH
2006-09-10 23:58 ` Eric W. Biederman [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=m1fyezclzq.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=akpm@osdl.org \
--cc=containers@lists.osdl.org \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
/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
all inboxes | Powered by JetHome®