1. 04 10月, 2015 1 次提交
  2. 27 9月, 2015 1 次提交
  3. 21 9月, 2015 1 次提交
  4. 13 9月, 2015 1 次提交
  5. 04 9月, 2015 1 次提交
  6. 31 8月, 2015 1 次提交
  7. 28 8月, 2015 1 次提交
  8. 24 8月, 2015 1 次提交
  9. 17 8月, 2015 1 次提交
  10. 14 8月, 2015 2 次提交
  11. 10 8月, 2015 1 次提交
  12. 07 8月, 2015 3 次提交
    • D
      modsign: Use single PEM file for autogenerated key · fb117949
      David Woodhouse 提交于
      The current rule for generating signing_key.priv and signing_key.x509 is
      a classic example of a bad rule which has a tendency to break parallel
      make. When invoked to create *either* target, it generates the other
      target as a side-effect that make didn't predict.
      
      So let's switch to using a single file signing_key.pem which contains
      both key and certificate. That matches what we do in the case of an
      external key specified by CONFIG_MODULE_SIG_KEY anyway, so it's also
      slightly cleaner.
      Signed-off-by: NDavid Woodhouse <David.Woodhouse@intel.com>
      Signed-off-by: NDavid Howells <dhowells@redhat.com>
      fb117949
    • D
    • D
      MODSIGN: Use PKCS#7 messages as module signatures · 3f1e1bea
      David Howells 提交于
      Move to using PKCS#7 messages as module signatures because:
      
       (1) We have to be able to support the use of X.509 certificates that don't
           have a subjKeyId set.  We're currently relying on this to look up the
           X.509 certificate in the trusted keyring list.
      
       (2) PKCS#7 message signed information blocks have a field that supplies the
           data required to match with the X.509 certificate that signed it.
      
       (3) The PKCS#7 certificate carries fields that specify the digest algorithm
           used to generate the signature in a standardised way and the X.509
           certificates specify the public key algorithm in a standardised way - so
           we don't need our own methods of specifying these.
      
       (4) We now have PKCS#7 message support in the kernel for signed kexec purposes
           and we can make use of this.
      
      To make this work, the old sign-file script has been replaced with a program
      that needs compiling in a previous patch.  The rules to build it are added
      here.
      Signed-off-by: NDavid Howells <dhowells@redhat.com>
      Tested-by: NVivek Goyal <vgoyal@redhat.com>
      3f1e1bea
  13. 03 8月, 2015 1 次提交
  14. 27 7月, 2015 1 次提交
  15. 22 7月, 2015 2 次提交
  16. 20 7月, 2015 1 次提交
  17. 13 7月, 2015 1 次提交
  18. 06 7月, 2015 2 次提交
  19. 22 6月, 2015 1 次提交
  20. 15 6月, 2015 1 次提交
  21. 08 6月, 2015 1 次提交
  22. 01 6月, 2015 1 次提交
  23. 25 5月, 2015 1 次提交
  24. 19 5月, 2015 1 次提交
  25. 11 5月, 2015 1 次提交
  26. 04 5月, 2015 1 次提交
  27. 29 4月, 2015 1 次提交
  28. 27 4月, 2015 2 次提交
    • P
      Makefile: Fix detection of clang when cross-compiling · ee4eb20d
      Paul Cercueil 提交于
      When the host's C compiler is clang, and when attempting to
      cross-compile Linux e.g. to MIPS with mipsel-linux-gcc, the Makefile
      would incorrectly detect the use of clang, which resulted in
      clang-specific flags being passed to mipsel-linux-gcc.
      
      This can be verified under Debian by installing the "clang" package,
      and then using it as the default compiler with:
      sudo update-alternatives --config cc
      
      This patch moves the detection of clang after the $(CC) variable is
      initialized to the name of the cross-compiler, so that the check applies
      to the cross-compiler and not the host's C compiler.
      
      v2: Move the detection of clang after the inclusion of the
      arch/*/Makefile (as they might set $(CROSS_COMPILE))
      Signed-off-by: NPaul Cercueil <paul@crapouillou.net>
      Signed-off-by: NMichal Marek <mmarek@suse.cz>
      ee4eb20d
    • L
      Linux 4.1-rc1 · b787f68c
      Linus Torvalds 提交于
      b787f68c
  29. 13 4月, 2015 1 次提交
  30. 09 4月, 2015 1 次提交
    • A
      jump_label: Allow jump labels to be used in assembly · c0ccf6f9
      Anton Blanchard 提交于
      To use jump labels in assembly we need the HAVE_JUMP_LABEL
      define, so we select a fallback version if the toolchain does
      not support them.
      
      Modify linux/jump_label.h so it can be included by assembly
      files. We also need to add -DCC_HAVE_ASM_GOTO to KBUILD_AFLAGS.
      Signed-off-by: NAnton Blanchard <anton@samba.org>
      Acked-by: NPeter Zijlstra (Intel) <peterz@infradead.org>
      Cc: Andrew Morton <akpm@linux-foundation.org>
      Cc: Linus Torvalds <torvalds@linux-foundation.org>
      Cc: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
      Cc: Peter Zijlstra <peterz@infradead.org>
      Cc: Thomas Gleixner <tglx@linutronix.de>
      Cc: benh@kernel.crashing.org
      Cc: catalin.marinas@arm.com
      Cc: davem@davemloft.net
      Cc: heiko.carstens@de.ibm.com
      Cc: jbaron@akamai.com
      Cc: linux@arm.linux.org.uk
      Cc: linuxppc-dev@lists.ozlabs.org
      Cc: liuj97@gmail.com
      Cc: mgorman@suse.de
      Cc: mmarek@suse.cz
      Cc: mpe@ellerman.id.au
      Cc: paulus@samba.org
      Cc: ralf@linux-mips.org
      Cc: rostedt@goodmis.org
      Cc: schwidefsky@de.ibm.com
      Cc: will.deacon@arm.com
      Link: http://lkml.kernel.org/r/1428551492-21977-2-git-send-email-anton@samba.orgSigned-off-by: NIngo Molnar <mingo@kernel.org>
      c0ccf6f9
  31. 07 4月, 2015 1 次提交
  32. 02 4月, 2015 1 次提交
  33. 30 3月, 2015 1 次提交
  34. 25 3月, 2015 1 次提交