1. 15 3月, 2014 1 次提交
  2. 08 10月, 2012 1 次提交
    • D
      X.509: Add simple ASN.1 grammar compiler · 4520c6a4
      David Howells 提交于
      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: NDavid Howells <dhowells@redhat.com>
      Signed-off-by: NRusty Russell <rusty@rustcorp.com.au>
      4520c6a4
  3. 19 5月, 2012 1 次提交
    • H
      x86, realmode: 16-bit real-mode code support for relocs tool · 6520fe55
      H. Peter Anvin 提交于
      A new option is added to the relocs tool called '--realmode'.
      This option causes the generation of 16-bit segment relocations
      and 32-bit linear relocations for the real-mode code. When
      the real-mode code is moved to the low-memory during kernel
      initialization, these relocation entries can be used to
      relocate the code properly.
      
      In the assembly code 16-bit segment relocations must be relative
      to the 'real_mode_seg' absolute symbol. Linear relocations must be
      relative to a symbol prefixed with 'pa_'.
      
      16-bit segment relocation is used to load cs:ip in 16-bit code.
      Linear relocations are used in the 32-bit code for relocatable
      data references. They are declared in the linker script of the
      real-mode code.
      
      The relocs tool is moved to arch/x86/tools/relocs.c, and added new
      target archscripts that can be used to build scripts needed building
      an architecture.  be compiled before building the arch/x86 tree.
      
      [ hpa: accelerating this because it detects invalid absolute
        relocations, a serious bug in binutils 2.22.52.0.x which currently
        produces bad kernels. ]
      Signed-off-by: NH. Peter Anvin <hpa@linux.intel.com>
      Link: http://lkml.kernel.org/r/1336501366-28617-2-git-send-email-jarkko.sakkinen@intel.comSigned-off-by: NJarkko Sakkinen <jarkko.sakkinen@intel.com>
      Signed-off-by: NH. Peter Anvin <hpa@linux.intel.com>
      Cc: <stable@vger.kernel.org>
      6520fe55
  4. 09 5月, 2012 2 次提交
  5. 25 4月, 2012 1 次提交
  6. 20 4月, 2012 1 次提交
  7. 03 5月, 2011 1 次提交
  8. 17 3月, 2011 1 次提交
    • M
      KBuild: silence "'scripts/unifdef' is up to date." · e1b702cf
      Mike Waychison 提交于
      While changing our build system over to use the headers_install target
      as part of our klibc build, the following message started showing up in
      our logs:
      
      make[2]: `scripts/unifdef' is up to date.
      
      It turns out that the build blindly invokes a recursive make on this
      target, which causes make to emit this message when the target is
      already up to date.  This isn't seen for most targets as the rest of the
      build relies primarily on the default target and on PHONY targets when
      invoking make recursively.
      
      Silence the above message when building unifdef as part of
      headers_install by hiding it behind a new PHONY target called
      "build_unifdef" that has an empty recipe.
      Signed-off-by: NMike Waychison <mikew@google.com>
      Acked-by: NWANG Cong <xiyou.wangcong@gmail.com>
      Signed-off-by: NMichal Marek <mmarek@suse.cz>
      e1b702cf
  9. 15 10月, 2010 1 次提交
    • S
      ftrace/x86: Add support for C version of recordmcount · 72441cb1
      Steven Rostedt 提交于
      This patch adds the support for the C version of recordmcount and
      compile times show ~ 12% improvement.
      
      After verifying this works, other archs can add:
      
       HAVE_C_MCOUNT_RECORD
      
      in its Kconfig and it will use the C version of recordmcount
      instead of the perl version.
      
      Cc: <linux-arch@vger.kernel.org>
      Cc: Michal Marek <mmarek@suse.cz>
      Cc: linux-kbuild@vger.kernel.org
      Cc: John Reiser <jreiser@bitwagon.com>
      Signed-off-by: NSteven Rostedt <rostedt@goodmis.org>
      72441cb1
  10. 16 9月, 2009 1 次提交
    • D
      sparc: Kill PROM console driver. · 09d3f3f0
      David S. Miller 提交于
      Many years ago when this driver was written, it had a use, but these
      days it's nothing but trouble and distributions should not enable it
      in any situation.
      
      Pretty much every console device a sparc machine could see has a
      bonafide real driver, making the PROM console hack unnecessary.
      
      If any new device shows up, we should write a driver instead of
      depending upon this crutch to save us.  We've been able to take care
      of this even when no chip documentation exists (sunxvr500, sunxvr2500)
      so there are no excuses.
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      09d3f3f0
  11. 03 5月, 2009 1 次提交
    • D
      Move dtc and libfdt sources from arch/powerpc/boot to scripts/dtc · 9fffb55f
      David Gibson 提交于
      The powerpc kernel always requires an Open Firmware like device tree
      to supply device information.  On systems without OF, this comes from
      a flattened device tree blob.  This blob is usually generated by dtc,
      a tool which compiles a text description of the device tree into the
      flattened format used by the kernel.  Sometimes, the bootwrapper makes
      small changes to the pre-compiled device tree blob (e.g. filling in
      the size of RAM).  To do this it uses the libfdt library.
      
      Because these are only used on powerpc, the code for both these tools
      is included under arch/powerpc/boot (these were imported and are
      periodically updated from the upstream dtc tree).
      
      However, the microblaze architecture, currently being prepared for
      merging to mainline also uses dtc to produce device tree blobs.  A few
      other archs have also mentioned some interest in using dtc.
      Therefore, this patch moves dtc and libfdt from arch/powerpc into
      scripts, where it can be used by any architecture.
      
      The vast bulk of this patch is a literal move, the rest is adjusting
      the various Makefiles to use dtc and libfdt correctly from their new
      locations.
      Signed-off-by: NDavid Gibson <david@gibson.dropbear.id.au>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      9fffb55f
  12. 07 4月, 2009 1 次提交
  13. 08 1月, 2009 1 次提交
    • S
      fix modules_install via NFS · 8b249b68
      Sam Ravnborg 提交于
      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: N"Rafael J. Wysocki" <rjw@sisk.pl>
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      Cc: David Woodhouse <dwmw2@infradead.org>
      8b249b68
  14. 27 8月, 2008 1 次提交
    • S
      selinux: add support for installing a dummy policy (v2) · 93c06cbb
      Serge E. Hallyn 提交于
      In August 2006 I posted a patch generating a minimal SELinux policy.  This
      week, David P. Quigley posted an updated version of that as a patch against
      the kernel.  It also had nice logic for auto-installing the policy.
      
      Following is David's original patch intro (preserved especially
      bc it has stats on the generated policies):
      
      se interested in the changes there were only two significant
      changes. The first is that the iteration through the list of classes
      used NULL as a sentinel value. The problem with this is that the
      class_to_string array actually has NULL entries in its table as place
      holders for the user space object classes.
      
      The second change was that it would seem at some point the initial sids
      table was NULL terminated. This is no longer the case so that iteration
      has to be done on array length instead of looking for NULL.
      
      Some statistics on the policy that it generates:
      
      The policy consists of 523 lines which contain no blank lines. Of those
      523 lines 453 of them are class, permission, and initial sid
      definitions. These lines are usually little to no concern to the policy
      developer since they will not be adding object classes or permissions.
      Of the remaining 70 lines there is one type, one role, and one user
      statement. The remaining lines are broken into three portions. The first
      group are TE allow rules which make up 29 of the remaining lines, the
      second is assignment of labels to the initial sids which consist of 27
      lines, and file system labeling statements which are the remaining 11.
      
      In addition to the policy.conf generated there is a single file_contexts
      file containing two lines which labels the entire system with base_t.
      
      This policy generates a policy.23 binary that is 7920 bytes.
      
      (then a few versions later...):
      
      The new policy is 587 lines (stripped of blank lines) with 476 of those
      lines being the boilerplate that I mentioned last time. The remaining
      111 lines have the 3 lines for type, user, and role, 70 lines for the
      allow rules (one for each object class including user space object
      classes), 27 lines to assign types to the initial sids, and 11 lines for
      file system labeling. The policy binary is 9194 bytes.
      
      Changelog:
      
      	Aug 26: Added Documentation/SELinux.txt
      	Aug 26: Incorporated a set of comments by Stephen Smalley:
      		1. auto-setup SELINUXTYPE=dummy
      		2. don't auto-install if selinux is enabled with
      			non-dummy policy
      		3. don't re-compute policy version
      		4. /sbin/setfiles not /usr/sbin/setfiles
      	Aug 22: As per JMorris comments, made sure make distclean
      		cleans up the mdp directory.
      		Removed a check for file_contexts which is now
      		created in the same file as the check, making it
      		superfluous.
      Signed-off-by: NSerge Hallyn <serue@us.ibm.com>
      Signed-off-by: NDavid Quigley <dpquigl@tycho.nsa.gov>
      Signed-off-by: NJames Morris <jmorris@namei.org>
      93c06cbb
  15. 01 10月, 2006 1 次提交
  16. 25 9月, 2006 2 次提交
  17. 17 12月, 2005 1 次提交
  18. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4