stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <gregkh@linuxfoundation.org>
To: fupan.li@windriver.com, ben@decadent.org.uk, fupanli@gmail.com,
	gregkh@linuxfoundation.org, jslaby@suse.cz,
	linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
	matt.fleming@intel.com, matt@codeblueprint.co.uk,
	stable@vger.kernel.org
Cc: <stable@vger.kernel.org>, <stable-commits@vger.kernel.org>
Subject: Patch "efi: fix 32bit kernel boot failed problem using efi" has been added to the 3.10-stable tree
Date: Sat, 08 Aug 2015 15:05:18 -0700	[thread overview]
Message-ID: <1439071518248231@kroah.com> (raw)
In-Reply-To: <1438653081-25746-1-git-send-email-fupan.li@windriver.com>


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.10-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.10 subdirectory.

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


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

From: Fupan Li <fupan.li@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.li@windriver.com>
Reviewed-by: Matt Fleming <matt.fleming@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.li@windriver.com are

queue-3.10/efi-fix-32bit-kernel-boot-failed-problem-using-efi.patch

  parent reply	other threads:[~2015-08-08 22:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-04  1:51 [PATCH V3 request from stable 3.10 to 3.14] efi: fix 32bit kernel boot failed problem using efi fupan.li
2015-08-04 17:12 ` Matt Fleming
2015-08-08 22:05 ` gregkh [this message]
2015-08-08 22:05 ` Patch "efi: fix 32bit kernel boot failed problem using efi" has been added to the 3.14-stable tree gregkh

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=1439071518248231@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=ben@decadent.org.uk \
    --cc=fupan.li@windriver.com \
    --cc=fupanli@gmail.com \
    --cc=jslaby@suse.cz \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt.fleming@intel.com \
    --cc=matt@codeblueprint.co.uk \
    --cc=stable-commits@vger.kernel.org \
    --cc=stable@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;
as well as URLs for NNTP newsgroup(s).