Re: 2.2.2 kernel is out
Geert Uytterhoeven (Geert.Uytterhoeven@cs.kuleuven.ac.be)
Wed, 24 Feb 1999 13:08:46 +0100 (CET)
On 24 Feb 1999, H. Peter Anvin wrote:
> Followup to: <Pine.LNX.4.05.9902232346280.10520-100000@laser.random>
> By author: Andrea Arcangeli <andrea@e-mind.com>
> In newsgroup: linux.dev.kernel
> >
> > The only _unluky_ thing :( is that my first fix (the one in 2.2.2) has
> > still a little window for a similar race again in down_interruptible() and
> > down_trylock(), and I should have fixed it completly only in the last
> > days. You can find my patch against 2.2.2-pre5 (or 2.2.2) on the list. The
> > new patch is quite simple and the race won't have the time impact somebody
> > in the meantime but it's still not perfect (even if closer). Excuse me.
> >
> > So I suggest all no-x86 arch developers to apply my latest semaphore patch
> > before starting fixing semaphores.
> >
> > Also I don't know if it worth to move the semaphore-helper.h to
> > include/linux. Doing that (using the spinlock everywhere) and so following
> > the x86 semaphore implementation, it would be semi-trivial for no-x86
> > maintainers to fix their trees without having to think (too much ;) about
> > the races.
>
> I guess it might have been preferrable to make a prepatch, ALERT all
> the non-x86 arch maintainers, and give them a day or two to cough up
> the patches? Obviously a timeout is necessary, but it'd make sense, I
> believe.
Exactly what I had in mind!
Greetings,
Geert
--
Geert Uytterhoeven Geert.Uytterhoeven@cs.kuleuven.ac.be
Wavelets, Linux/{m68k~Amiga,PPC~CHRP} http://www.cs.kuleuven.ac.be/~geert/
Department of Computer Science -- Katholieke Universiteit Leuven -- Belgium
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/