1. 23 Jun, 2017 1 commit
  2. 26 Feb, 2016 1 commit
  3. 28 Sep, 2015 1 commit
    • Ben Hutchings's avatar
      DocBook: Use a fixed encoding for output · b479bfd0
      Ben Hutchings authored
      Currently the encoding of documents generated by DocBook depends on
      the current locale.  Make the output reproducible independently of
      the locale, by setting the encoding to UTF-8 (LC_CTYPE=C.UTF-8) by
      preference, or ASCII (LC_CTYPE=C) as a fallback.
      LC_CTYPE can normally be overridden by LC_ALL, but the top-level
      Makefile unsets that.
      Signed-off-by: default avatarBen Hutchings <ben@decadent.org.uk>
      [jc: added check-lc_ctype to .gitignore]
      Signed-off-by: default avatarJonathan Corbet <corbet@lwn.net>
  4. 26 Aug, 2015 1 commit
  5. 08 Aug, 2014 1 commit
    • Vivek Goyal's avatar
      bin2c: move bin2c in scripts/basic · 8370edea
      Vivek Goyal authored
      This patch series does not do kernel signature verification yet.  I plan
      to post another patch series for that.  Now distributions are already
      signing PE/COFF bzImage with PKCS7 signature I plan to parse and verify
      those signatures.
      Primary goal of this patchset is to prepare groundwork so that kernel
      image can be signed and signatures be verified during kexec load.  This
      should help with two things.
      - It should allow kexec/kdump on secureboot enabled machines.
      - In general it can help even without secureboot. By being able to verify
        kernel image signature in kexec, it should help with avoiding module
        signing restrictions. Matthew Garret showed how to boot into a custom
        kernel, modify first kernel's memory and then jump back to old kernel and
        bypass any policy one wants to.
      This patch (of 15):
      Kexec wants to use bin2c and it wants to use it really early in the build
      process. See arch/x86/purgatory/ code in later patches.
      So move bin2c in scripts/basic so that it can be built very early and
      be usable by arch/x86/purgatory/
      Signed-off-by: default avatarVivek Goyal <vgoyal@redhat.com>
      Cc: Borislav Petkov <bp@suse.de>
      Cc: Michael Kerrisk <mtk.manpages@gmail.com>
      Cc: Yinghai Lu <yinghai@kernel.org>
      Cc: Eric Biederman <ebiederm@xmission.com>
      Cc: H. Peter Anvin <hpa@zytor.com>
      Cc: Matthew Garrett <mjg59@srcf.ucam.org>
      Cc: Greg Kroah-Hartman <greg@kroah.com>
      Cc: Dave Young <dyoung@redhat.com>
      Cc: WANG Chao <chaowang@redhat.com>
      Cc: Baoquan He <bhe@redhat.com>
      Cc: Andy Lutomirski <luto@amacapital.net>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
  6. 08 Oct, 2012 1 commit
    • David Howells's avatar
      X.509: Add simple ASN.1 grammar compiler · 4520c6a4
      David Howells authored
      Add a simple ASN.1 grammar compiler.  This produces a bytecode output that can
      be fed to a decoder to inform the decoder how to interpret the ASN.1 stream it
      is trying to parse.
      Action functions can be specified in the grammar by interpolating:
      	({ foo })
      after a type, for example:
      	SubjectPublicKeyInfo ::= SEQUENCE {
      		algorithm		AlgorithmIdentifier,
      		subjectPublicKey	BIT STRING ({ do_key_data })
      The decoder is expected to call these after matching this type and parsing the
      contents if it is a constructed type.
      The grammar compiler does not currently support the SET type (though it does
      support SET OF) as I can't see a good way of tracking which members have been
      encountered yet without using up extra stack space.
      Currently, the grammar compiler will fail if more than 256 bytes of bytecode
      would be produced or more than 256 actions have been specified as it uses
      8-bit jump values and action indices to keep space usage down.
      Signed-off-by: default avatarDavid Howells <dhowells@redhat.com>
      Signed-off-by: default avatarRusty Russell <rusty@rustcorp.com.au>
  7. 08 May, 2012 1 commit
  8. 19 Apr, 2012 1 commit
  9. 02 May, 2011 1 commit
  10. 25 Nov, 2010 1 commit
  11. 07 Oct, 2009 1 commit
    • Dick Streefland's avatar
      kconfig: simplification of scripts/extract-ikconfig · 7b76bfc8
      Dick Streefland authored
      I've rewritten the extract-ikconfig script to extract the kernel
      configuration from a kernel compiled with CONFIG_IKCONFIG. The main
      motivation for the rewrite was to remove the dependency on the
      external C program binoffset.c, which is compiled on the initial run.
      The binoffset executable is invoked with a relative path, which means
      that the old script can only be run from the top of the kernel tree,
      and only when you have write permission in the scripts directory.
      The new script uses tr/grep/tail/zcat only, and can be invoked from
      anywhere. The binoffset.c program has been removed. This script
      requires GNU grep 2.5 (released 2002-03-13) or higher, because the -o
      option was introduced in that version.
      Signed-off-by: default avatarDick Streefland <dick@streefland.net>
      LKML-Reference: <20091006203540.GA14634@streefland.net>
      Tested-by: default avatarSteven Rostedt <rostedt@goodmis.org>
      Cc: Sam Ravnborg <sam@ravnborg.org>
      Signed-off-by: default avatarSteven Rostedt <rostedt@goodmis.org>
  12. 26 Jun, 2009 1 commit
  13. 06 Apr, 2009 1 commit
  14. 07 Jan, 2009 1 commit
    • Sam Ravnborg's avatar
      fix modules_install via NFS · 8b249b68
      Sam Ravnborg authored
      Rafael reported:
      I get the following error from 'make modules_install' on my test boxes:
        HOSTCC  firmware/ihex2fw
      /home/rafael/src/linux-2.6/firmware/ihex2fw.c:268: fatal error: opening dependency file firmware/.ihex2fw.d: Read-only file system
      compilation terminated.
      make[3]: *** [firmware/ihex2fw] Error 1
      make[2]: *** [_modinst_post] Error 2
      make[1]: *** [sub-make] Error 2
      make: *** [all] Error 2
      where the configuration is that the kernel is compiled on a build box
      with 'make O=<destdir> -j5' and then <destdir> is mounted over NFS read-only by
      each test box (full path to this directory is the same on the build box and on
      the test boxes).  Then, I cd into <destdir>, run 'make modules_install' and get
      the error above.
      The issue turns out to be that we when we install firmware pick
      up the list of firmware blobs from firmware/Makefile.
      And this triggers the Makefile rules to update ihex2fw.
      There were two solutions for this issue:
      1) Move the list of firmware blobs to a separate file
      2) Avoid ihex2fw rebuild by moving it to scripts
      As I seriously beleive that the list of firmware blobs should be
      done in a fundamental different way solution 2) was selected.
      Reported-and-tested-by: default avatar"Rafael J. Wysocki" <rjw@sisk.pl>
      Signed-off-by: default avatarSam Ravnborg <sam@ravnborg.org>
      Cc: David Woodhouse <dwmw2@infradead.org>
  15. 09 Feb, 2008 1 commit
  16. 03 Oct, 2006 1 commit
  17. 03 Jan, 2006 1 commit
  18. 18 Oct, 2005 1 commit