Date: Wed, 09 Apr 2003 15:45:29 -0400 From: Mike Tancsa <mike@sentex.net> To: Tor.Egge@cvsup.no.freebsd.org Cc: stable@FreeBSD.org Subject: Re: 3ware 3dmd broken in STABLE ( due to cvs commit: src/sys/kern kern_descrip.c kern_fork.c ) Message-ID: <5.2.0.9.0.20030409154415.077e1a08@marble.sentex.ca> In-Reply-To: <20030409193402E.tegge@cvsup.no.freebsd.org> References: <5.2.0.9.0.20030409142819.07c59c60@marble.sentex.ca> <5.2.0.9.0.20030409140404.07e83b18@marble.sentex.ca> <20030409181835K.tegge@cvsup.no.freebsd.org> <5.2.0.9.0.20030409142819.07c59c60@marble.sentex.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
At 07:34 PM 09/04/2003 +0000, Tor.Egge@cvsup.no.freebsd.org wrote:
> > Thanks. Is there a work around where the lock leakage can be fixed and
> the
> > 3ware daemon can work ? I dont know who (if anyone) has the source
> code to
> > the 3dmd program, is this something that could be easily fixed in it
> ? Are
> > there any other programs that will break as a result of your commit as
> well ?
>
>Changing the rfork() system call in kern_fork.c to add the RFTHREAD
>flag instead of returning EINVAL might allow the 3ware daemon to work.
>
>Another alternative is to modify the 3dmd binary to add the RFTHREAD
>flag in rfork() at 0x806b39c.
What tools would I use to 'try this at home' ?
---Mike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5.2.0.9.0.20030409154415.077e1a08>