Date: Wed, 14 Nov 2001 21:18:22 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
To: Alfred Perlstein <bright@mu.org>
Cc: Greg Lehey <grog@FreeBSD.ORG>, Bruce Evans <bde@zeta.org.au>, Peter Wemm <peter@wemm.org>, Robert Watson <rwatson@FreeBSD.ORG>, freebsd-arch@FreeBSD.ORG
Subject: Re: cur{thread/proc}, or not.
Message-ID: <200111150518.fAF5IMW18730@apollo.backplane.com>
References: <20011112165530.B34657-100000@delplex.bde.org> <200111121009.fACA9SI75024@apollo.backplane.com> <20011111191735.00D053807@overcee.netplex.com.au> <20011112165530.B34657-100000@delplex.bde.org> <200111121009.fACA9SI75024@apollo.backplane.com> <20011115132945.C33267@monorchid.lemis.com> <20011114231057.K13393@elvis.mu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
:If you want to see why curproc sucks then please investigate what
:happens when you NDINIT a nameidata with another thread pointer
:other than your own, then perform a vn_open. kablooey!
:
:My recent addition of vn_open_cred and modification of nfs_lock.c
:was to get around this badness of the API.
:
:--
:-Alfred Perlstein [alfred@freebsd.org]
I'm not sure this is a fair argument. Just about all the code
in the system taking a struct thread * pointer assumes that the
thread is the current thread and so avoid much of the locking that
they would normally have to do on it. Passing some other thread
to a good chunk of this code will have very weird broken results.
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200111150518.fAF5IMW18730>