From owner-freebsd-net Sun Jan 20 15:29:31 2002 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 511D737B404 for ; Sun, 20 Jan 2002 15:29:28 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.11.4/8.11.4) id g0KNTLO33136; Sun, 20 Jan 2002 18:29:21 -0500 (EST) (envelope-from wollman) Date: Sun, 20 Jan 2002 18:29:21 -0500 (EST) From: Garrett Wollman Message-Id: <200201202329.g0KNTLO33136@khavrinen.lcs.mit.edu> To: Archie Cobbs Cc: freebsd-net@FreeBSD.ORG Subject: Re: netgraph: how to setsockopt on ksocket node ? In-Reply-To: <200201202308.g0KN8uc09321@arch20m.dellroad.org> References: <135740000.1011562445@blues.viagenie.qc.ca> <200201202308.g0KN8uc09321@arch20m.dellroad.org> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org < said: > But it's interesting the soalloc() is called with 'p != 0' > as an argument. p is never 0 or else you would have already > panic'd... you'd panic later on, too, referencing 'p->p_ucred'. All of the credential frobbing stuff was added much later. At the time I wrote that `p != 0', it was definitely possible for socreate() to be called from interrupt context, and thus without any idea of a `current process'. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message