From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Sun,  6 Sep 2015 06:14:48 -0700
To: 9fans@9fans.net
Message-ID: <958267eb934f1630a72ca99ac828b3b2@brasstown.quanstro.net>
In-Reply-To: <82a662b665bce9245bfda986a0604ddb@felloff.net>
References: <82a662b665bce9245bfda986a0604ddb@felloff.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] Privalloc(2) and rfork(RFPROC|RFMEM) (was: a pair nec
	bugs)
Topicbox-Message-UUID: 691f97b2-ead9-11e9-9d60-3106f5b1d025

On Sat Sep  5 23:33:50 PDT 2015, cinap_lenrek@felloff.net wrote:
> hey charles!
>
> is privfree() broken? it appears it chains the slots together,
> but only the calling process will get a correct chain. the chain
> head (privs) is shared (in bss) and seen by all process so the
> others will get corrupted chains (chain link is private) no?
>
> i wonder what the intended use for privfree() was. theres no
> code using it.

i think the logic in tprivalloc is what was intended.

- erik