This is a note to let you know that I've just added the patch titled

    efi: fix 32bit kernel boot failed problem using efi

to the 3.14-stable tree which can be found at:
    
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

The filename of the patch is:
     efi-fix-32bit-kernel-boot-failed-problem-using-efi.patch
and it can be found in the queue-3.14 subdirectory.

If you, or anyone else, feels it should not be added to the stable tree,
please let <sta...@vger.kernel.org> know about it.


>From fupan...@windriver.com  Sat Aug  8 15:03:02 2015
From: <fupan...@windriver.com>
Date: Tue, 4 Aug 2015 09:51:21 +0800
Subject: efi: fix 32bit kernel boot failed problem using efi
To: <gre...@linuxfoundation.org>, <m...@codeblueprint.co.uk>
Cc: <jsl...@suse.cz>, <linux-...@vger.kernel.org>, <sta...@vger.kernel.org>, 
<linux-kernel@vger.kernel.org>, <fupa...@gmail.com>, <b...@decadent.org.uk>
Message-ID: <1438653081-25746-1-git-send-email-fupan...@windriver.com>

From: Fupan Li <fupan...@windriver.com>

Commit 35d5134b7d5a
("x86/efi: Correct EFI boot stub use of code32_start")
imported a bug, which will cause 32bit kernel boot failed
using efi method. It should use the label's address instead
of the value stored in the label to caculate the address of
code32_start.

Signed-off-by: Fupan Li <fupan...@windriver.com>
Reviewed-by: Matt Fleming <matt.flem...@intel.com>
---
 arch/x86/boot/compressed/head_32.S |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- a/arch/x86/boot/compressed/head_32.S
+++ b/arch/x86/boot/compressed/head_32.S
@@ -54,7 +54,7 @@ ENTRY(efi_pe_entry)
        call    reloc
 reloc:
        popl    %ecx
-       subl    reloc, %ecx
+       subl    $reloc, %ecx
        movl    %ecx, BP_code32_start(%eax)
 
        sub     $0x4, %esp


Patches currently in stable-queue which might be from fupan...@windriver.com are

queue-3.14/efi-fix-32bit-kernel-boot-failed-problem-using-efi.patch
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to