Date: Mon, 30 Sep 2002 22:45:34 -0700 (PDT) From: Don Lewis <dl-freebsd@catspoiler.org> To: jmallett@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: World broken at libkvm Message-ID: <200210010545.g915jYvU012168@gw.catspoiler.org> In-Reply-To: <20021001035729.D34502A88D@canning.wemm.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 30 Sep, Peter Wemm wrote: > Juli Mallett wrote: >> And now fixed. All we have to look out for now is someone doing something >> that exposes some sort of functional difference, but I don't anticipate it. > I suggest you turn WITNESS on, and stress the system. If you get *new* > 'could sleep' stuff or other lock order problems, then there are still > significant regressions to be fixed. The last thing we need during the > 'please stabilize 5.0' drive is newly added problems. If other folks are > seeing new ones, please report them here (not to me, I already get too much > email :-]). I suggest looking especially closely at the sigio stuff. Even the old code has a lock order reversal problem when I/O to a pipe wants to signal the process at the other end of the pipe. I thought a lot about that problem and never found a clean fix. The sigio stuff could be even nastier if you need to allocate memory in the signal code because the sigio can be invoked by the reception of a packet from the network, which is not handled in a process context ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200210010545.g915jYvU012168>