Re: [patch 4/5] x86: use BOOTMEM_EXCLUSIVE on 32-bit

From: Ingo Molnar
Date: Mon Jun 23 2008 - 04:11:22 EST



* Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> wrote:

> On Sun, 22 Jun 2008, Greg KH wrote:
> >
> > > You will also need the patch from http://lkml.org/lkml/2008/6/21/103 to
> > > make sure reserve_bootmem() is not void (*)().
> >
> > Ok, let me know when that goes into Linus's tree please.
>
> It already is: 71c2742f5e6348d76ee62085cf0a13e5eff0f00e.

thanks. This patch (which was not a build fix but an infrastructure fix
that the kexec fix in arch/x86 depended on) is well-tested as well, it
was queued in -tip on June 10th:

| commit 91d48fc80f22817332170082e10de60a75851640
| Author: Bernhard Walle <bwalle@xxxxxxx>
| Date: Sun Jun 8 15:46:29 2008 +0200
| CommitDate: Tue Jun 10 14:41:56 2008 +0200
|
| bootmem: add return value to reserve_bootmem_node()
|
| This patch changes the function reserve_bootmem_node() from void to
| int, returning -ENOMEM if the allocation fails.
|
| Signed-off-by: Bernhard Walle <bwalle@xxxxxxx>
| Signed-off-by: Ingo Molnar <mingo@xxxxxxx>

so it is a -stable candidate just as much as the kexec fix. (These are
all fixes for long-standing problems so i guess it can go all the way
back to all stable kernels that are being maintained.)

Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/