Messages in this thread | | | Date | Fri, 18 Jan 2013 22:51:20 +0100 | Subject | Re: linux-next: Tree for Jan 18 [MODSIGN: KEYS:] | From | Sedat Dilek <> |
| |
On Fri, Jan 18, 2013 at 10:43 PM, Sedat Dilek <sedat.dilek@gmail.com> wrote: > On Fri, Jan 18, 2013 at 5:37 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote: >> Hi all, >> >> Changes since 20130117: >> >> Undropped tree: samung >> >> The powerpc tree still had a build failure. >> >> The driver-core tree gained a build failure for which I applied a merge >> fix patch. >> >> The gpio-lw tree gained a build failure so I used the version from >> next-20130117. >> >> The samsung tree lost the majority of its conflicts but gained more >> against the arm-soc and slave-dma tree. >> >> ---------------------------------------------------------------------------- >> > > I pulled Linux v3.8-rc4 (one commit) into next-20130118. > > When CONFIG_SYSTEM_TRUSTED_KEYRING=n I see these error-messages on AMD64: > > CC security/keys/keyring.o > CC kernel/module_signing.o > CC [M] arch/x86/kvm/i8259.o > kernel/module_signing.c: In function 'request_asymmetric_key': > kernel/module_signing.c:161:36: error: 'system_trusted_keyring' > undeclared (first use in this function) > kernel/module_signing.c:161:36: note: each undeclared identifier is > reported only once for each function it appears in > make[3]: *** [kernel/module_signing.o] Error 1 > make[2]: *** [kernel] Error 2 > make[2]: *** Waiting for unfinished jobs.... >
Culprit seems to be...
commit d6941c0c6bd42c725e45240a86c4add92e9bfb3e "KEYS: Separate the kernel signature checking keyring from module signing"
- Sedat -
[1] http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=commitdiff;h=d6941c0c6bd42c725e45240a86c4add92e9bfb3e
| |