*BSD News Article 10479


Return to BSD News archive

Received: by minnie.vk1xwt.ampr.org with NNTP
	id AA186 ; Fri, 29 Jan 93 07:00:24 EST
Newsgroups: comp.unix.bsd
Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!uwm.edu!caen!saimiri.primate.wisc.edu!usenet.coe.montana.edu!gemini.oscs.montana.edu!osynw
From: osynw@gemini.oscs.montana.edu (Nate Williams)
Subject: Re: [386bsd] X broken with new patchkit ?
Message-ID: <1993Jan28.162938.964@coe.montana.edu>
Keywords: n
Sender: usenet@coe.montana.edu (USENET News System)
Organization: Montana State University
References: <4374@wzv.win.tue.nl> <1993Jan28.091650.29630@gmd.de>
Date: Thu, 28 Jan 1993 16:29:38 GMT
Lines: 25

>The patchkit has (at least one) builtin incompatibility regarding the behaviour
>of select(2). In the patchkit there is a change in the kernel that lets select
>wait on a process's pid rather than a pointer to its struct proc. This is
>actually a patch which should be 386bsd-0.2 stuff, and shouldn't have gone
>into the patchkit. 

According to the comments sent by Bill, this fixed a problem where telnet
was walking on top of another data structure
I quote (with slight modification for politeness sake)

To fix obscure telnet bug (it "messes up" another data structure in the process,
because it's using a "freed" process e.g. free()):

Unfortunately, for lack of time and lack of familiarity with the code, I
didn't know what would be affected by the fix.  As far as the original
distribution, (this is what the patchkit is for), the only routine
that still needs to be fixed is the com driver.  (If X is hogging all
the resources with the new patchkit, get Chris's new com driver, since
it contains the fixed select stuff)

Nate
-- 
osynw@terra.oscs.montana.edu |  A hacker w/out a home. 
work: (406) 994-5991         |  Keeper of the Unofficial 386BSD Bug Report
home: (406) 586-0579         |  Please send bugs and/or fixes you find.