From: James Hogan <james.hogan@imgtec.com>
To: David Howells <dhowells@redhat.com>,
Rusty Russell <rusty@rustcorp.com.au>,
Andrew Morton <akpm@linux-foundation.org>,
"Joe Perches" <joe@perches.com>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Jean Delvare <khali@linux-fr.org>,
Ralf Baechle <ralf@linux-mips.org>
Cc: <linux-kernel@vger.kernel.org>, James Hogan <james.hogan@imgtec.com>
Subject: [PATCH 0/2] modsign: fix missing symbol prefix
Date: Fri, 23 Nov 2012 12:08:14 +0000 [thread overview]
Message-ID: <1353672496-10789-1-git-send-email-james.hogan@imgtec.com> (raw)
These patches fix linker errors on blackfin and metag when module
signing is enabled. This is due to the use of symbol prefixes on these
architectures, and the asm in modsign_pubkey.c not prefixing one.
The first patch defines SYMBOL_PREFIX in linux/kernel based on
CONFIG_SYMBOL_PREFIX to avoid duplicated ifdef'ery all over the place.
The second patch uses SYMBOL_PREFIX to fix modsign_pubkey.c.
I'm not entirely sure linux/kernel.h is the best place for it, but there
are two other similar defines in there to avoid #ifdefs.
James Hogan (2):
linux/kernel.h: define SYMBOL_PREFIX
modsign: add symbol prefix to certificate list
include/linux/kernel.h | 7 +++++++
kernel/modsign_pubkey.c | 4 ++--
2 files changed, 9 insertions(+), 2 deletions(-)
--
1.7.7.6
next reply other threads:[~2012-11-23 12:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-23 12:08 James Hogan [this message]
2012-11-23 12:08 ` [PATCH 1/2] linux/kernel.h: define SYMBOL_PREFIX James Hogan
2012-11-23 12:08 ` [PATCH 2/2] modsign: add symbol prefix to certificate list James Hogan
2012-12-03 2:38 ` [PATCH 0/2] modsign: fix missing symbol prefix Rusty Russell
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=1353672496-10789-1-git-send-email-james.hogan@imgtec.com \
--to=james.hogan@imgtec.com \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=joe@perches.com \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=ralf@linux-mips.org \
--cc=rusty@rustcorp.com.au \
/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
all inboxes | Powered by JetHome®