From: tip-bot for Matt Fleming <matt.fleming@intel.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@kernel.org,
jordan.l.justen@intel.com, tglx@linutronix.de,
hpa@linux.intel.com, matt.fleming@intel.com
Subject: [tip:x86/efi] x86, efi: Fix NumberOfRvaAndSizes field in PE32 header for EFI_STUB
Date: Mon, 26 Mar 2012 15:21:17 -0700 [thread overview]
Message-ID: <tip-e47bb0bda46bf50f81671db502d0c903e0a32604@git.kernel.org> (raw)
In-Reply-To: <1332520506-6472-4-git-send-email-jordan.l.justen@intel.com>
Commit-ID: e47bb0bda46bf50f81671db502d0c903e0a32604
Gitweb: http://git.kernel.org/tip/e47bb0bda46bf50f81671db502d0c903e0a32604
Author: Matt Fleming <matt.fleming@intel.com>
AuthorDate: Fri, 23 Mar 2012 09:35:06 -0700
Committer: H. Peter Anvin <hpa@linux.intel.com>
CommitDate: Mon, 26 Mar 2012 13:10:02 -0700
x86, efi: Fix NumberOfRvaAndSizes field in PE32 header for EFI_STUB
We've actually got six data directories in the header, not one. Even
though the firmware loader doesn't seem to mind, when we come to sign
the kernel image the signing tool thinks that there is no Certificate
Table data directory, even though we've allocated space for one.
Signed-off-by: Matt Fleming <matt.fleming@intel.com>
Link: http://lkml.kernel.org/r/1332520506-6472-4-git-send-email-jordan.l.justen@intel.com
Reviewed-by: Jordan Justen <jordan.l.justen@intel.com>
Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
---
| 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
--git a/arch/x86/boot/header.S b/arch/x86/boot/header.S
index 4ceb56e..8bbea6a 100644
--- a/arch/x86/boot/header.S
+++ b/arch/x86/boot/header.S
@@ -189,7 +189,7 @@ extra_header_fields:
.quad 0 # SizeOfHeapCommit
#endif
.long 0 # LoaderFlags
- .long 0x1 # NumberOfRvaAndSizes
+ .long 0x6 # NumberOfRvaAndSizes
.quad 0 # ExportTable
.quad 0 # ImportTable
parent reply other threads:[~2012-03-26 22:21 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1332520506-6472-4-git-send-email-jordan.l.justen@intel.com>]
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=tip-e47bb0bda46bf50f81671db502d0c903e0a32604@git.kernel.org \
--to=matt.fleming@intel.com \
--cc=hpa@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jordan.l.justen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
/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