Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 15 Jul 2004 21:18:29 -0600
From:      Scott Long <scottl@samsco.org>
To:        Tim Robbins <tjr@freebsd.org>
Cc:        Kris Kennaway <kris@obsecurity.org>
Subject:   Re: 5.3-RELEASE TODO
Message-ID:  <40F74905.1080506@samsco.org>
In-Reply-To: <40F74071.70306@samsco.org>
References:  <200407151424.i6FEOdoq060881@fledge.watson.org> <20040715220447.GA32888@xor.obsecurity.org> <6.1.0.6.1.20040715151650.03fae510@popserver.sfu.ca> <20040716010707.GA22394@cat.robbins.dropbear.id.au> <40F74071.70306@samsco.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Scott Long wrote:
> Tim Robbins wrote:
> 
>> On Thu, Jul 15, 2004 at 03:20:19PM -0700, Colin Percival wrote:
>>
>>> At 15:04 15/07/2004, Kris Kennaway wrote:
>>>
>>>> * linprocfs [...]
>>>>      if (pvd->pvd_pid != NO_PID) {
>>>>               if ((proc = pfind(pvd->pvd_pid)) == NULL)
>>>>                       PFS_RETURN (ENOENT);
>>>> -->             vap->va_uid = proc->p_ucred->cr_ruid;
>>>>
>>>> rwatson has a patch that works around this particular null pointer
>>>> deref, but the underlying cause is not addressed.
>>>
>>>
>>> This looks like the "embryonic processes are added to allproc and
>>> p_hash too soon" bug (cf. kern/68364).  Last I heard, tjr was going
>>> to fix this in the next few days.
>>
>>
>>
>> I was going to, but it turns out that my original solution of not
>> putting "embryonic" processes on allproc would further break 
>> checkdirs() --
>> there are already a few kinds of races that can happen there, and I don't
>> want to add more.
>>
>>
>> Tim
> 
> 
> Please don't take this the wrong way, but would you consider using a
> null-modem serial cable and SLIP or PPP instead?  PLIP has been
> neglected nice it was first introduced, and I doubt that it has much
> life left.  Setting up SLIP and PPP is trivially easy and has a much
> better chance of working between OS's.
> 
> Scott
> 

Ok, I've officially been in front of the computer for too long today.
This response was actually meant for a different message.  Sorry for the
confusion.

Scott



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?40F74905.1080506>