Return to BSD News archive
Xref: sserve comp.bugs.4bsd:1938 comp.os.386bsd.bugs:541 Newsgroups: comp.bugs.4bsd,comp.os.386bsd.bugs Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!haven.umd.edu!darwin.sura.net!zaphod.mps.ohio-state.edu!cs.utexas.edu!wotan.compaq.com!hackney From: hackney@wotan.compaq.com (Greg Hackney) Subject: Re: flock broken - I could use some help Message-ID: <1993Apr22.183734.4448@wotan.compaq.com> Organization: Compaq Computers References: <C5t8wH.Hs@moxie.hou.tx.us> <1993Apr21.184636.1121@cs.few.eur.nl> Date: Thu, 22 Apr 1993 18:37:34 GMT Lines: 19 I wrote: >> It appears that flock() is causing panic's and reboots. >> Below is some test code to make it fail. In article <1993Apr21.184636.1121@cs.few.eur.nl> pk@cs.few.eur.nl writes: > The problem is a dangling pointer left in the lockf structure belonging to > the current lock holder. > ------- ufs_lockf.c ------- > *** /tmp/da16367 Wed Apr 21 20:36:22 1993 > --- ufs/ufs_lockf.c Wed Apr 21 20:35:47 1993 I applied your code fragment to ufs_lockf.c. However it didn't solve the problem, as my system still panics and reboots using the aforementioned test code. -- Greg