public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [patch 16/19] x86 setup: handle boot loaders which set up the stack incorrectly
Date: Thu, 15 Nov 2007 08:42:14 -0800	[thread overview]
Message-ID: <20071115164214.GF24087@suse.de> (raw)
In-Reply-To: <473BF4C5.4080909@zytor.com>

On Wed, Nov 14, 2007 at 11:27:01PM -0800, H. Peter Anvin wrote:
> Greg KH wrote:
>> -stable review patch.  If anyone has any objections, please let us know.
>> ------------------
>> From: H. Peter Anvin <hpa@zytor.com>
>> patch 6b6815c6d5d1dc209701d1661a7a0e09a295db2f in mainline.
>> Apparently some specific versions of LILO enter the kernel with a
>> stack pointer that doesn't match the rest of the segments.  Make our
>> best attempt at untangling the resulting mess.
>> Signed-off-by: H. Peter Anvin <hpa@zytor.com>
>> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
>
> Just FYI:
>
> It has been reported that while this patch fixes old LILO, and possibly 
> some other boot loaders (unknown), it has also broken older versions of 
> SYSLINUX: they still boot, but the command line is truncated (exactly how 
> much depends on the BIOS, but typical values are around 130 bytes.)
>
> This is definitely traceable to a bug in SYSLINUX that was already fixed in 
> release 3.50 (the current version of SYSLINUX is 3.52).
>
> I have chosen to leave the patch in mainline, rather than trying yet 
> another recipe and hope it doesn't break on some other random combination 
> of bootloaders, since:
>
> a) SYSLINUX is generally easily updated, compared to other bootloaders;
> b) The failure mode is less severe (it still boots.)
>
> ... however, you may choose to call differently.

I have no objection to keeping this patch in the tree, as it fixes a
real problem, and matches the upstream kernel version.

thanks,

greg k-h

  reply	other threads:[~2007-11-15 16:43 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20071115054813.977066477@mini.kroah.org>
2007-11-15  6:14 ` [patch 00/19] 2.6.23-stable review, arch specific stuff Greg KH
2007-11-15  6:14   ` [patch 01/19] Fix sparc64 niagara optimized RAID xor asm Greg KH
2007-11-15  6:14   ` [patch 02/19] Fix sparc64 MAP_FIXED handling of framebuffer mmaps Greg KH
2007-11-15  6:14   ` [patch 03/19] MIPS: MT: Fix bug in multithreaded kernels Greg KH
2007-11-15  6:14   ` [patch 04/19] MIPS: R1: Fix hazard barriers to make kernels work on R2 also Greg KH
2007-11-15  6:14   ` [patch 05/19] POWERPC: Fix handling of stfiwx math emulation Greg KH
2007-11-15  6:14   ` [patch 06/19] POWERPC: Make sure to of_node_get() the result of pci_device_to_OF_node() Greg KH
2007-11-15  6:14   ` [patch 07/19] UML - Stop using libc asm/page.h Greg KH
2007-11-15  6:14   ` [patch 08/19] UML - Fix kernel vs libc symbols clash Greg KH
2007-11-15  6:14   ` [patch 09/19] UML - stop using libc asm/user.h Greg KH
2007-11-15  6:14   ` [patch 10/19] UML - kill subprocesses on exit Greg KH
2007-11-15  6:14   ` [patch 11/19] xen: add batch completion callbacks Greg KH
2007-11-15  6:15   ` [patch 12/19] xen: deal with stale cr3 values when unpinning pagetables Greg KH
2007-11-15  6:15   ` [patch 13/19] xen: fix incorrect vcpu_register_vcpu_info hypercall argument Greg KH
2007-11-15  6:15   ` [patch 14/19] xfs: eagerly remove vmap mappings to avoid upsetting Xen Greg KH
2007-11-15  6:15   ` [patch 15/19] x86: fix global_flush_tlb() bug Greg KH
2007-11-15  6:15   ` [patch 16/19] x86 setup: handle boot loaders which set up the stack incorrectly Greg KH
2007-11-15  7:27     ` H. Peter Anvin
2007-11-15 16:42       ` Greg KH [this message]
2007-11-15  6:15   ` [patch 17/19] x86 setup: sizeof() is unsigned, unbreak comparisons Greg KH
2007-11-15  6:15   ` [patch 18/19] x86: fix TSC clock source calibration error Greg KH
2007-11-15  6:15   ` [patch 19/19] revert "x86_64: allocate sparsemem memmap above 4G" Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20071115164214.GF24087@suse.de \
    --to=gregkh@suse.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox