Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932090AbWIJVnE (ORCPT ); Sun, 10 Sep 2006 17:43:04 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932094AbWIJVnE (ORCPT ); Sun, 10 Sep 2006 17:43:04 -0400 Received: from mail.kroah.org ([69.55.234.183]:26583 "EHLO perch.kroah.org") by vger.kernel.org with ESMTP id S932090AbWIJVnD (ORCPT ); Sun, 10 Sep 2006 17:43:03 -0400 Date: Sun, 10 Sep 2006 14:37:46 -0700 From: Greg KH To: "Eric W. Biederman" Cc: Andrew Morton , linux-kernel@vger.kernel.org, Linux Containers , linux-usb-devel@lists.sourceforge.net, Greg Kroah-Hartman Subject: Re: [PATCH] usb: Fixup usb so it uses struct pid Message-ID: <20060910213746.GA9565@kroah.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.13 (2006-08-11) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1128 Lines: 31 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 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 thanks, greg k-h - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/