Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759726AbXH0SQO (ORCPT ); Mon, 27 Aug 2007 14:16:14 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758008AbXH0SP7 (ORCPT ); Mon, 27 Aug 2007 14:15:59 -0400 Received: from zeniv.linux.org.uk ([195.92.253.2]:53604 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757847AbXH0SP6 (ORCPT ); Mon, 27 Aug 2007 14:15:58 -0400 Date: Mon, 27 Aug 2007 19:15:44 +0100 From: Al Viro To: Dean Nelson Cc: akpm@linux-foundation.org, linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, tony.luck@intel.com, jes@sgi.com Subject: Re: [PATCH 1/4] export __put_task_struct for XPMEM Message-ID: <20070827181544.GH21089@ftp.linux.org.uk> References: <20070827155622.GA25589@sgi.com> <20070827155933.GB25589@sgi.com> <20070827161327.GG21089@ftp.linux.org.uk> <20070827181056.GA30176@sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070827181056.GA30176@sgi.com> User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1540 Lines: 32 On Mon, Aug 27, 2007 at 01:10:56PM -0500, Dean Nelson wrote: > On Mon, Aug 27, 2007 at 05:13:28PM +0100, Al Viro wrote: > > On Mon, Aug 27, 2007 at 10:59:33AM -0500, Dean Nelson wrote: > > > This patch exports __put_task_struct as it is needed by XPMEM. > > > > > > Signed-off-by: Dean Nelson > > > > > > --- > > > > > > One struct file_operations registered by XPMEM, xpmem_open(), calls > > > 'get_task_struct(current->group_leader)' and another, xpmem_flush(), calls > > > 'put_task_struct(tg->group_leader)'. > > > > Does it? Well, then open the file in question and start doing close(dup(fd)) > > in a loop. Won't take long for an oops... > > Actually it won't oops. And that's because when the file is opened, > xpmem_open() creates a structure for that thread group, and when > xpmem_flush() is called on the close() it first looks for that structure > and if it finds it then it does what it needs to do (which includes the > put_task_struct() call) and then finishes off by destroying the structure. > So for subsequent closes xpmem_flush() returns without calling > put_task_struct(). Then what kind of protection does it get you? It can be called immediately after the call of ->open(), so you can't rely on it being there for any operations. Makes no sense... - 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/