Date: Wed, 7 Jun 2000 16:58:41 -0400 (EDT) From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> To: Bernd Walter <ticso@cicely8.cicely.de> Cc: "G.B.Naidu" <gbnaidu@sasi.com>, hackers@FreeBSD.ORG, net@FreeBSD.ORG Subject: Re: [REPOST] Re: How do I get port inside kernel.... (fwd) Message-ID: <200006072058.QAA72060@khavrinen.lcs.mit.edu> In-Reply-To: <20000607220906.A98783@cicely8.cicely.de> References: <Pine.LNX.4.21.0006071011570.763-100000@pcd75.sasi.com> <20000607220906.A98783@cicely8.cicely.de>
next in thread | previous in thread | raw e-mail | index | archive | help
<<On Wed, 7 Jun 2000 22:09:06 +0200, Bernd Walter <ticso@cicely8.cicely.de> said: >> current process? Is it safe if I use proc0 to pass the proc structure to >> call socreate() and sobind()? How safe it is to use curproc >> structure? Somebody mentioned that it will not work in interrupt >> handlers. proc0 is passed because I didn't think things completely through when the socket layer was taught not to accept process arguments. In most if not all cases the process parameter should be passed as nil, rather than &proc0, because the code uses this value to determine whether or not it is safe to sleep. Some of the code, however, is buggy in that it does not check for a null process pointer and proceeds to dereference it. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200006072058.QAA72060>