1. 01 3月, 2008 5 次提交
  2. 29 2月, 2008 1 次提交
  3. 27 2月, 2008 21 次提交
  4. 26 2月, 2008 13 次提交
    • L
      Merge branch 'for-linus' of git://oss.sgi.com:8090/xfs/xfs-2.6 · 7704a8b6
      Linus Torvalds 提交于
      * 'for-linus' of git://oss.sgi.com:8090/xfs/xfs-2.6:
        [XFS] Undo bit ops cleanup mod due to regression on 32-bit powermac
        [XFS] Undo bit ops cleanup mod due to regression on 32-bit powermac
        Remove empty file fs/xfs/Makefile-linux-2.6.
      7704a8b6
    • L
      Merge branch 'for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4 · adefe11c
      Linus Torvalds 提交于
      * 'for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4:
        ext4: add missing ext4_journal_stop()
        ext4: ext4_find_next_zero_bit needs an aligned address on some arch
        ext4: set EXT4_EXTENTS_FL only for directory and regular files
        ext4: Don't mark filesystem error if fallocate fails
        ext4: Fix BUG when writing to an unitialized extent
        ext4: Don't use ext4_dec_count() if not needed
        ext4: modify block allocation algorithm for the last group
        ext4: Don't claim block from group which has corrupt bitmap
        ext4: Get journal write access before modifying the extent tree
        ext4: Fix memory and buffer head leak in callers to ext4_ext_find_extent()
        ext4: Don't leave behind a half-created inode if ext4_mkdir() fails
        ext4: Fix kernel BUG at fs/ext4/mballoc.c:910!
        ext4: Fix locking hierarchy violation in ext4_fallocate()
        Remove incorrect BKL comments in ext4
      adefe11c
    • L
      Merge branch 'upstream-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev · 3d6ce332
      Linus Torvalds 提交于
      * 'upstream-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev:
        Revert "power_state: get rid of write-only variable in SATA"
        make atapi_dmadir static
      3d6ce332
    • L
      Merge branch 'v2.6.25-rc3-lockdep' of... · 3fca96ee
      Linus Torvalds 提交于
      Merge branch 'v2.6.25-rc3-lockdep' of git://git.kernel.org/pub/scm/linux/kernel/git/peterz/linux-2.6-lockdep
      
      * 'v2.6.25-rc3-lockdep' of git://git.kernel.org/pub/scm/linux/kernel/git/peterz/linux-2.6-lockdep:
        Subject: lockdep: include all lock classes in all_lock_classes
        lockdep: increase MAX_LOCK_DEPTH
      3fca96ee
    • L
      Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394-2.6 · 98c1fc93
      Linus Torvalds 提交于
      * 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394-2.6:
        firewire: fix NULL pointer deref. and resource leak
        Documentation: correction to debugging-via-ohci1394
        ieee1394: sbp2: fix rescan-scsi-bus
        firewire: fw-sbp2: fix NULL pointer deref. in scsi_remove_device
        firewire: fw-sbp2: fix NULL pointer deref. in slave_alloc
        firewire: fw-sbp2: (try to) avoid I/O errors during reconnect
        firewire: fw-sbp2: enforce a retry of __scsi_add_device if bus generation changed
        firewire: fw-sbp2: sort includes
        firewire: fw-sbp2: logout and login after failed reconnect
        firewire: fw-sbp2: don't add scsi_device twice
        firewire: fw-sbp2: log bus_id at management request failures
        firewire: fw-sbp2: wait for completion of fetch agent reset
        ieee1394: sbp2: add INQUIRY delay workaround
        firewire: fw-sbp2: add INQUIRY delay workaround
        firewire: log GUID of new devices
        firewire: fw-sbp2: don't retry login or reconnect after unplug
        firewire: fix "kobject_add failed for fw* with -EEXIST"
        firewire: fw-sbp2: fix logout before login retry
        firewire: fw-sbp2: unsigned int vs. unsigned
      98c1fc93
    • L
      Merge git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-x86 · 7c811e4b
      Linus Torvalds 提交于
      * git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-x86: (24 commits)
        x86: no robust/pi futex for real i386 CPUs
        x86: fix boot failure on 486 due to TSC breakage
        x86: fix build on non-C locales.
        x86: make c_idle.work have a static address.
        x86: don't save unreliable stack trace entries
        x86: don't make swapper_pg_pmd global
        x86: don't print a warning when MTRR are blank and running in KVM
        x86: fix execve with -fstack-protect
        x86: fix vsyscall wreckage
        x86: rename KERNEL_TEXT_SIZE => KERNEL_IMAGE_SIZE
        x86: fix spontaneous reboot with allyesconfig bzImage
        x86: remove double-checking empty zero pages debug
        x86: notsc is ignored on common configurations
        x86/mtrr: fix kernel-doc missing notation
        x86: handle BIOSes which terminate e820 with CF=1 and no SMAP
        x86: add comments for NOPs
        x86: don't use P6_NOPs if compiling with CONFIG_X86_GENERIC
        x86: require family >= 6 if we are using P6 NOPs
        x86: do not promote TM3x00/TM5x00 to i686-class
        x86: hpet fix docbook comment
        ...
      7c811e4b
    • L
      Merge git://git.kernel.org/pub/scm/linux/kernel/git/mingo/linux-2.6-sched · 37c00b84
      Linus Torvalds 提交于
      * git://git.kernel.org/pub/scm/linux/kernel/git/mingo/linux-2.6-sched:
        latencytop: change /proc task_struct access method
        latencytop: fix memory leak on latency proc file
        latencytop: fix kernel panic while reading latency proc file
        sched: add declaration of sched_tail to sched.h
        sched: fix signedness warnings in sched.c
        sched: clean up __pick_last_entity() a bit
        sched: remove duplicate code from sched_fair.c
        sched: make early bootup sched_clock() use safer
      37c00b84
    • T
      printk: fix possible printk overrun · cf3680b9
      Tejun Heo 提交于
      printk recursion detection prepends message to printk_buf and offsets
      printk_buf when actual message is printed but it forgets to trim buffer
      length accordingly. This can result in overrun in extreme cases. Fix it.
      
      [ mingo@elte.hu:
      
        bug was introduced by me via:
      
         commit 32a76006
         Author: Ingo Molnar <mingo@elte.hu>
         Date:   Fri Jan 25 21:07:58 2008 +0100
      
             printk: make printk more robust by not allowing recursion
      ]
      Signed-off-by: NTejun Heo <htejun@gmail.com>
      Signed-off-by: NIngo Molnar <mingo@elte.hu>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      cf3680b9
    • T
      x86: no robust/pi futex for real i386 CPUs · f18edc95
      Thomas Gleixner 提交于
      Real i386 CPUs do not have cmpxchg instructions. Catch it before
      crashing on an invalid opcode.
      Signed-off-by: NIngo Molnar <mingo@elte.hu>
      Signed-off-by: NThomas Gleixner <tglx@linutronix.de>
      f18edc95
    • M
      x86: fix boot failure on 486 due to TSC breakage · 12c247a6
      Mikael Pettersson 提交于
       > Diffing dmesg between git7 and git8 doesn't sched any light since
       > git8 also removed the printouts of the x86 caps as they were being
       > initialised and updated. I'm currently adding those printouts back
       > in the hope of seeing where and when the caps get broken.
      
      That turned out to be very illuminating:
      
       --- dmesg-2.6.24-git7	2008-02-24 18:01:25.295851000 +0100
       +++ dmesg-2.6.24-git8	2008-02-24 18:01:25.530358000 +0100
       ...
       CPU: After generic identify, caps: 00000003 00000000 00000000 00000000 00000000 00000000 00000000 00000000
      
       CPU: After all inits, caps: 00000003 00000000 00000000 00000000 00000000 00000000 00000000 00000000
      +CPU: After applying cleared_cpu_caps, caps: 00000013 00000000 00000000 00000000 00000000 00000000 00000000 00000000
      
      Notice how the TSC cap bit goes from Off to On.
      
      (The first two lines are printout loops from -git7 forward-ported
      to -git8, the third line is the same printout loop added just after
      the xor-with-cleared_cpu_caps[] loop.)
      
      Here's how the breakage occurs:
      1. arch/x86/kernel/tsc_32.c:tsc_init() sees !cpu_has_tsc,
         so bails and calls setup_clear_cpu_cap(X86_FEATURE_TSC).
      2. include/asm-x86/cpufeature.h:setup_clear_cpu_cap(bit) clears
         the bit in boot_cpu_data and sets it in cleared_cpu_caps
      3. arch/x86/kernel/cpu/common.c:identify_cpu() XORs all caps
         in with cleared_cpu_caps
         HOWEVER, at this point c->x86_capability correctly has TSC
         Off, cleared_cpu_caps has TSC On, so the XOR incorrectly
         sets TSC to On in c->x86_capability, with disastrous results.
      
      The real bug is that clearing bits with XOR only works if the
      bits are known to be 1 prior to the XOR, and that's not true here.
      
      A simple fix is to convert the XOR to AND-NOT instead. The following
      patch does that, and allows my 486 to boot 2.6.25-rc kernels again.
      
      [ mingo@elte.hu: fixed a similar bug in setup_64.c as well. ]
      
      The breakage was introduced via commit 7d851c8d.
      Signed-off-by: NMikael Pettersson <mikpe@it.uu.se>
      Signed-off-by: NIngo Molnar <mingo@elte.hu>
      12c247a6
    • P
      x86: fix build on non-C locales. · 03994f01
      Priit Laes 提交于
      For some locales regex range [a-zA-Z] does not work as it is supposed to.
      so we have to use [:alnum:] and [:xdigit:] to make it work as intended.
      
      [1] http://en.wikipedia.org/wiki/Estonian_alphabetSigned-off-by: NIngo Molnar <mingo@elte.hu>
      03994f01
    • G
      x86: make c_idle.work have a static address. · 2b775a27
      Glauber Costa 提交于
      Currently, c_idle is declared in the stack, and thus, have no static address.
      
      Peter Zijlstra points out this simple solution, in which c_idle.work
      is initializated separatedly. Note that the INIT_WORK macro has a static
      declaration of a key inside.
      Signed-off-by: NGlauber Costa <gcosta@redhat.com>
      Acked-by: NPeter Zijlstra <pzijlstr@redhat.com>
      Signed-off-by: NIngo Molnar <mingo@elte.hu>
      2b775a27
    • V
      x86: don't save unreliable stack trace entries · 1650743c
      Vegard Nossum 提交于
      Currently, there is no way for print_stack_trace() to determine whether
      a given stack trace entry was deemed reliable or not, simply because
      save_stack_trace() does not record this information. (Perhaps needless
      to say, this makes the saved stack traces A LOT harder to read, and
      probably with no other benefits, since debugging features that use
      save_stack_trace() most likely also require frame pointers, etc.)
      
      This patch reverts to the old behaviour of only recording the reliable trace
      entries for saved stack traces.
      Signed-off-by: NVegard Nossum <vegardno@ifi.uio.no>
      Acked-by: NArjan van de Ven <arjan@linux.intel.com>
      Signed-off-by: NIngo Molnar <mingo@elte.hu>
      1650743c