1. 17 7月, 2007 1 次提交
    • H
      generic bug: use show_regs() instead of dump_stack() · 608e2619
      Heiko Carstens 提交于
      The current generic bug implementation has a call to dump_stack() in case a
      WARN_ON(whatever) gets hit.  Since report_bug(), which calls dump_stack(),
      gets called from an exception handler we can do better: just pass the
      pt_regs structure to report_bug() and pass it to show_regs() in case of a
      warning.  This will give more debug informations like register contents,
      etc...  In addition this avoids some pointless lines that dump_stack()
      emits, since it includes a stack backtrace of the exception handler which
      is of no interest in case of a warning.  E.g.  on s390 the following lines
      are currently always present in a stack backtrace if dump_stack() gets
      called from report_bug():
      
       [<000000000001517a>] show_trace+0x92/0xe8)
       [<0000000000015270>] show_stack+0xa0/0xd0
       [<00000000000152ce>] dump_stack+0x2e/0x3c
       [<0000000000195450>] report_bug+0x98/0xf8
       [<0000000000016cc8>] illegal_op+0x1fc/0x21c
       [<00000000000227d6>] sysc_return+0x0/0x10
      Acked-by: NJeremy Fitzhardinge <jeremy@goop.org>
      Acked-by: NHaavard Skinnemoen <hskinnemoen@atmel.com>
      Cc: Andi Kleen <ak@suse.de>
      Cc: Kyle McMartin <kyle@parisc-linux.org>
      Cc: Paul Mackerras <paulus@samba.org>
      Cc: Paul Mundt <lethal@linux-sh.org>
      Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>
      Signed-off-by: NHeiko Carstens <heiko.carstens@de.ibm.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      608e2619
  2. 12 7月, 2007 2 次提交
    • A
      PCI: read revision ID by default · b8a3a521
      Auke Kok 提交于
      Currently there are 97 occurrences where drivers need the pci
      revision ID. We can do this once for all devices. Even the pci
      subsystem needs the revision several times for quirks. The extra
      u8 member pads out nicely in the pci_dev struct.
      Signed-off-by: NAuke Kok <auke-jan.h.kok@intel.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      
      b8a3a521
    • M
      PCI: Make pcibios_add_platform_entries() return errors · a2cd52ca
      Michael Ellerman 提交于
      Currently pcibios_add_platform_entries() returns void, but could fail,
      so instead have it return an int and propagate errors up to
      pci_create_sysfs_dev_files().
      
      Fixes:
      arch/powerpc/kernel/pci_64.c: In function 'pcibios_add_platform_entries':
      arch/powerpc/kernel/pci_64.c:878: warning: ignoring return value of
      	'device_create_file', declared with attribute warn_unused_result
      arch/powerpc/kernel/pci_32.c: In function 'pcibios_add_platform_entries':
        arch/powerpc/kernel/pci_32.c:1043: warning: ignoring return value of
      	'device_create_file', declared with attribute warn_unused_result
      Signed-off-by: NMichael Ellerman <michael@ellerman.id.au>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      
      a2cd52ca
  3. 11 7月, 2007 1 次提交
  4. 10 7月, 2007 13 次提交
  5. 03 7月, 2007 2 次提交
  6. 02 7月, 2007 1 次提交
  7. 30 6月, 2007 1 次提交
  8. 29 6月, 2007 9 次提交
  9. 28 6月, 2007 4 次提交
  10. 26 6月, 2007 2 次提交
    • P
      [POWERPC] Fix subtle FP state corruption bug in signal return on SMP · ae62fbb5
      Paul Mackerras 提交于
      This fixes a bug which can cause corruption of the floating-point state
      on return from a signal handler.  If we have a signal handler that has
      used the floating-point registers, and it happens to context-switch to
      another task while copying the interrupted floating-point state from the
      user stack into the thread struct (e.g. because of a page fault, or
      because it gets preempted), the context switch code will think that the
      FP registers contain valid FP state that needs to be copied into the
      thread_struct, and will thus overwrite the values that the signal return
      code has put into the thread_struct.
      
      This can occur because we clear the MSR bits that indicate the presence
      of valid FP state after copying the state into the thread_struct.  To fix
      this we just move the clearing of the MSR bits to before the copy.  A
      similar potential problem also occurs with the Altivec state, and this
      fixes that in the same way.
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      ae62fbb5
    • T
      [POWERPC] Fix VDSO gettimeofday() when called with NULL struct timeval · 74609f45
      Tony Breeds 提交于
      Consider the prototype for gettimeofday():
      	int gettimofday(struct timeval *tv, struct timezone *tz);
      
      Although it is valid to call with /either/ tv or tz being NULL, and
      the C version of sys_gettimeofday() supports this, the current version
      of gettimeofday() in the VDSO will SEGV if called with a NULL tv.
      
      This adds a check for tv being NULL so that it doesn't SEGV.
      Signed-off-by: NTony Breeds <tony@bakeyournoodle.com>
      Acked-by: NBenjamin Herrenschmidt <benh@kernel.crashing.org>
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      74609f45
  11. 25 6月, 2007 4 次提交