From: Pete Zaitcev <zaitcev@redhat.com>
To: ebiederm@xmission.com (Eric W. Biederman)
Cc: Andrew Morton <akpm@osdl.org>,
Linux Containers <containers@lists.osdl.org>,
Greg Kroah-Hartman <gregkh@suse.de>,
linux-kernel@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net
Subject: Re: [PATCH] usb: Fixup usb so it uses struct pid
Date: Sun, 10 Sep 2006 11:12:49 -0700 [thread overview]
Message-ID: <20060910111249.c2e9c5f2.zaitcev@redhat.com> (raw)
In-Reply-To: <m1hczgfi3h.fsf@ebiederm.dsl.xmission.com>
On Sat, 09 Sep 2006 22:42:10 -0600, ebiederm@xmission.com (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.
... which is completely all right in this case. We used to have an
implementation which tried to hold onto the task_struct and that sucked.
It is only possible for the task to disappear without notifying devio
under very special conditions only, which involve forking with parent
exiting. In other words, even a buggy application won't trigger this
without deliberately trying. And when it happens, uid checks make sure
that other users are not affected.
> Holding a reference
> to a struct pid avoid that problem, and paves the way
> for implementing a pid namespace.
That may be useful.
The patch itself seems straightforward if we can trust your struct
pid thingies. If OpenVZ people approve, I don't mind.
-- Pete
next prev parent reply other threads:[~2006-09-10 18:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-10 4:42 [PATCH] usb: Fixup usb so it uses struct pid Eric W. Biederman
2006-09-10 18:12 ` Pete Zaitcev [this message]
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
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=20060910111249.c2e9c5f2.zaitcev@redhat.com \
--to=zaitcev@redhat.com \
--cc=akpm@osdl.org \
--cc=containers@lists.osdl.org \
--cc=ebiederm@xmission.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