Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 29 May 2007 00:54:58 +0000 (UTC)
From:      Tor Egge <Tor.Egge@cvsup.no.freebsd.org>
To:        attilio@freebsd.org
Cc:        jroberson@chesapeake.net, current@freebsd.org
Subject:   Re: Panic on -CURRENT after LDT changes
Message-ID:  <20070529.005458.74657868.Tor.Egge@cvsup.no.freebsd.org>
In-Reply-To: <3bbf2fe10705281553n49ed5408qde560f53931b7d71@mail.gmail.com>
References:  <20070528.162023.41711345.Tor.Egge@cvsup.no.freebsd.org> <465B4450.90800@FreeBSD.org> <3bbf2fe10705281553n49ed5408qde560f53931b7d71@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
> Tor,
> I've updated the patch. Can you please redownload it and test/review:
> http://users.gufi.org/~rookie/works/patches/schedlock/ldt2.diff

Looking at the diff between the old ldt2.diff and the new ldt2.diff,
the change seems reasonable.

i386_ldt_grow() has another problem if multiple processes share a user LDT.
The old ldt is freed while still referenced by the CPUs.  This might cause
problems, e.g. with threaded linux binaries.

- Tor Egge



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070529.005458.74657868.Tor.Egge>