Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758729AbYG1W75 (ORCPT ); Mon, 28 Jul 2008 18:59:57 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752752AbYG1W7t (ORCPT ); Mon, 28 Jul 2008 18:59:49 -0400 Received: from mx1.redhat.com ([66.187.233.31]:34872 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752276AbYG1W7t (ORCPT ); Mon, 28 Jul 2008 18:59:49 -0400 Organization: Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903 From: David Howells To: Pavel Emelyanov cc: dhowells@redhat.com, jmorris@redhat.com, linux-kernel@vger.kernel.org Subject: Request for documentation of PID handling functions X-Mailer: MH-E 8.0.3+cvs; nmh 1.3; GNU Emacs 23.0.50 Date: Mon, 28 Jul 2008 23:59:46 +0100 Message-ID: <21590.1217285986@redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 678 Lines: 25 Hi Pavel, Can you please provide documentation for the PID handling functions you supplied in commit: 7af5729474b5b8ad385adadab78d6e723e7655a3 In particular I'd like to know what locks are required when. I'm trying to determine if in this piece of code: read_lock(&tasklist_lock); ret = 0; if (pid != task_pid_vnr(current)) ret = -EPERM; read_unlock(&tasklist_lock); the lock of tasklist_lock is necessary. David -- 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/