From: Herbert Poetzl (herbert_at_13thfloor.at)
Date: Fri 12 Dec 2003 - 20:21:00 GMT
On Fri, Dec 12, 2003 at 08:10:09PM +0000, Jonathan Sambrook wrote:
[ incredibly important info zapped here ]
> > I totally agree that uts_sem isn't the apropriate
> > to use in this place(s), but I don't see how this
> > could cause a deadlock/panic as there is nothing
> > to lock/panic if the rw sem is held for write ...
> Neither do I, but the call from exit.c seems to lock.
hmm, guess I'll have to investigate this further,
anyway, your changes won't do any harm, and if it
works for you, please apply them ...
> > please correct me if you see any crash/lock condition
> > there ...
> My machines running with these write locks replaced by a spinlock have
> been up for over two days now, instead of less than a minute. No other
> > what would be interesting is, how does vs1.3.0
> > behave in your tests, as it replaced the allocation
> > scheme completely (so no assign/alloc and no rw
> > uts_sem to fix ;)
> Yes. Will examine on Monday. But need to go live on some reall machines
> soon too...
Vserver mailing list