1. 23 10月, 2010 6 次提交
  2. 21 10月, 2010 1 次提交
  3. 18 10月, 2010 8 次提交
  4. 17 10月, 2010 2 次提交
    • T
      arm: Use ARCH_IRQ_INIT_FLAGS · 032fa360
      Thomas Gleixner 提交于
      The core code now initializes the requested number of interrupts and
      sets the flags in irq_desc.status which are requested by the
      architecture via ARCH_IRQ_INIT_FLAGS.
      
      Add ARCH_IRQ_INIT_FLAGS and remove the loop which sets those flags
      after the irq descriptors are allocated.
      
      [ This patch should have been in the original irq rework and got
        dropped accidentaly ]
      Signed-off-by: NThomas Gleixner <tglx@linutronix.de>
      Cc: Russell King <linux@arm.linux.org.uk>
      Cc: Linus Walleij <linus.walleij@stericsson.com>
      Cc: Anand Gadiyar <gadiyar@ti.com>
      032fa360
    • A
      genirq, ARM: Fix boot on ARM platforms · 05d0ca85
      Anand Gadiyar 提交于
      Commit b683de2b in linux-next as of 20101014 (genirq: Query
      arch for number of early descriptors) seems to have broken
      bootup on several ARM boards - my beagleboard gives the
      following dump with earlyprintk:
      
       NR_IRQS:402
       Unable to handle kernel NULL pointer dereference at virtual
       address 00000028 pgd = c0004000
       [00000028] *pgd=00000000
       Internal error: Oops: 5 [#1]
       last sysfs file:
       Modules linked in:
       CPU: 0    Not tainted
       (2.6.36-rc7-next-20101014-linux-next-20101012+ #40) PC is at
       init_IRQ+0x14/0x48 LR is at start_kernel+0x150/0x2c0
       [...]
      
      We seem to be using desc->status without assigning desc to
      anything. Fix this by adding back the code that was originally
      there.
      Signed-off-by: NAnand Gadiyar <gadiyar@ti.com>
      Tested-by: NLinus Walleij <linus.walleij@stericsson.com>
      Cc: Russell King <linux@arm.linux.org.uk>
      Cc: linux-arm-kernel@lists.infradead.org
      LKML-Reference: <1287077397-21781-1-git-send-email-gadiyar@ti.com>
      Signed-off-by: NIngo Molnar <mingo@elte.hu>
      05d0ca85
  5. 15 10月, 2010 1 次提交
    • L
      Don't dump task struct in a.out core-dumps · 0eead9ab
      Linus Torvalds 提交于
      akiphie points out that a.out core-dumps have that odd task struct
      dumping that was never used and was never really a good idea (it goes
      back into the mists of history, probably the original core-dumping
      code).  Just remove it.
      
      Also do the access_ok() check on dump_write().  It probably doesn't
      matter (since normal filesystems all seem to do it anyway), but he
      points out that it's normally done by the VFS layer, so ...
      
      [ I suspect that we should possibly do "vfs_write()" instead of
        calling ->write directly.  That also does the whole fsnotify and write
        statistics thing, which may or may not be a good idea. ]
      
      And just to be anal, do this all for the x86-64 32-bit a.out emulation
      code too, even though it's not enabled (and won't currently even
      compile)
      Reported-by: Nakiphie <akiphie@lavabit.com>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      0eead9ab
  6. 13 10月, 2010 2 次提交
  7. 12 10月, 2010 20 次提交