Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
tag: v2.6.25-rc5

Mar 10, 2008

  1. Linux 2.6.25-rc5

    Linus Torvalds authored
  2. Do not include linux/backing-dev.h twice

    Don't include linux/backing-dev.h twice in mm/filemap.c, it's pointless.
    
    Signed-off-by: Jesper Juhl <jesper.juhl@gmail.com>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
    Jesper Juhl authored Linus Torvalds committed

Mar 09, 2008

  1. Merge git://git.kernel.org/pub/scm/linux/kernel/git/tglx/linux-2.6-hrt

    * git://git.kernel.org/pub/scm/linux/kernel/git/tglx/linux-2.6-hrt:
      time: remove obsolete CLOCK_TICK_ADJUST
      time: don't touch an offlined CPU's ts->tick_stopped in tick_cancel_sched_timer()
      time: prevent the loop in timespec_add_ns() from being optimised away
      ntp: use unsigned input for do_div()
    Linus Torvalds authored
  2. Merge git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6

    * git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6:
      [CRYPTO] skcipher: Fix section mismatches
    Linus Torvalds authored
  3. alpha: fix iommu-related boot panic

    This fixes a boot panic due to a typo in the recent iommu patchset from
    FUJITA Tomonori <tomof@acm.org> - the code used dma_get_max_seg_size()
    instead of dma_get_seg_boundary().
    
    It also removes a couple of unnecessary BUG_ON() and ALIGN() macros.
    
    Signed-off-by: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
    Reported-and-tested-by: Bob Tracy <rct@frus.com>
    Acked-by: FUJITA Tomonori <tomof@acm.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
    Ivan Kokshaysky authored Linus Torvalds committed
  4. cpu hotplug: adjust root-domain->online span in response to hotplug e…

    …vent
    
    We currently set the root-domain online span automatically when the
    domain is added to the cpu if the cpu is already a member of
    cpu_online_map.
    
    This was done as a hack/bug-fix for s2ram, but it also causes a problem
    with hotplug CPU_DOWN transitioning.  The right way to fix the original
    problem is to actually respond to CPU_UP events, instead of CPU_ONLINE,
    which is already too late.
    
    This solves the hung reboot regression reported by Andrew Morton and
    others.
    
    Signed-off-by: Gregory Haskins <ghaskins@novell.com>
    Acked-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
    Signed-off-by: Ingo Molnar <mingo@elte.hu>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
    Gregory Haskins authored Linus Torvalds committed
  5. time: remove obsolete CLOCK_TICK_ADJUST

    The first version of the ntp_interval/tick_length inconsistent usage patch was
    recently merged as bbe4d18
    
    http://git.kernel.org/gitweb.cgi?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=bbe4d18ac2e058c56adb0cd71f49d9ed3216a405
    
    While the fix did greatly improve the situation, it was correctly pointed out
    by Roman that it does have a small bug: If the users change clocksources after
    the system has been running and NTP has made corrections, the correctoins made
    against the old clocksource will be applied against the new clocksource,
    causing error.
    
    The second attempt, which corrects the issue in the NTP_INTERVAL_LENGTH
    definition has also made it up-stream as commit
    e13a2e6
    
    http://git.kernel.org/gitweb.cgi?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=e13a2e61dd5152f5499d2003470acf9c838eab84
    
    Roman has correctly pointed out that CLOCK_TICK_ADJUST is calculated
    based on the PIT's frequency, and isn't really relevant to non-PIT
    driven clocksources (that is, clocksources other then jiffies and pit).
    
    This patch reverts both of those changes, and simply removes
    CLOCK_TICK_ADJUST.
    
    This does remove the granularity error correction for users of PIT and Jiffies
    clocksource users, but the granularity error but for the majority of users, it
    should be within the 500ppm range NTP can accommodate for.
    
    For systems that have granularity errors greater then 500ppm, the
    "ntp_tick_adj=" boot option can be used to compensate.
    
    [johnstul@us.ibm.com: provided changelog]
    [mattilinnanvuori@yahoo.com: maek ntp_tick_adj static]
    Signed-off-by: Roman Zippel <zippel@linux-m68k.org>
    Acked-by: john stultz <johnstul@us.ibm.com>
    Signed-off-by: Matti Linnanvuori <mattilinnanvuori@yahoo.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Cc: mingo@elte.hu
    Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
    Roman Zippel authored Thomas Gleixner committed
  6. time: don't touch an offlined CPU's ts->tick_stopped in tick_cancel_s…

    …ched_timer()
    
    Silences WARN_ONs in rcu_enter_nohz() and rcu_exit_nohz(), which appeared
    before caused by (repeated) calls to:
            $ echo 0 > /sys/devices/system/cpu/cpu1/online
            $ echo 1 > /sys/devices/system/cpu/cpu1/online
    
    Signed-off-by: Karsten Wiese <fzu@wemgehoertderstaat.de>
    Cc: johnstul@us.ibm.com
    Cc: Rafael Wysocki <rjw@sisk.pl>
    Cc: Steven Rostedt <rostedt@goodmis.org>
    Cc: Ingo Molnar <mingo@elte.hu>
    Acked-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
    Karsten Wiese authored Thomas Gleixner committed
  7. segher

    time: prevent the loop in timespec_add_ns() from being optimised away

    Since some architectures don't support __udivdi3().
    
    Signed-off-by: Segher Boessenkool <segher@kernel.crashing.org>
    Cc: john stultz <johnstul@us.ibm.com>
    Cc: Ingo Molnar <mingo@elte.hu>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
    segher authored Thomas Gleixner committed
  8. ntp: use unsigned input for do_div()

    The kernel NTP code shouldn't hand 64-bit *signed* values to do_div().  Make it
    instead hand 64-bit unsigned values.  This gets rid of a couple of warnings.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Cc: Roman Zippel <zippel@linux-m68k.org>
    Cc: Ingo Molnar <mingo@elte.hu>
    Cc: john stultz <johnstul@us.ibm.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
    David Howells authored Thomas Gleixner committed

Mar 08, 2008

  1. Fix waitid si_code regression

    In commit ee7c82d ("wait_task_stopped:
    simplify and fix races with SIGCONT/SIGKILL/untrace"), the magic (short)
    cast when storing si_code was lost in wait_task_stopped.  This leaks the
    in-kernel CLD_* values that do not match what userland expects.
    
    Signed-off-by: Roland McGrath <roland@redhat.com>
    Cc: Oleg Nesterov <oleg@tv-sign.ru>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
    Roland McGrath authored Linus Torvalds committed
  2. Herbert Xu

    [CRYPTO] skcipher: Fix section mismatches

    The previous patch to move chainiv and eseqiv into blkcipher created
    a section mismatch for the chainiv exit function which was also called
    from __init.  This patch removes the __exit marking on it.
    
    Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
    herbertx authored
  3. x86_64: make ptrace always sign-extend orig_ax to 64 bits

    This makes 64-bit ptrace calls setting the 64-bit orig_ax field for a
    32-bit task sign-extend the low 32 bits up to 64.  This matches what a
    64-bit debugger expects when tracing a 32-bit task.
    
    This follows on my "x86_64 ia32 syscall restart fix".  This didn't
    matter until that was fixed.
    
    The debugger ignores or zeros the high half of every register slot it
    sets (including the orig_rax pseudo-register) uniformly.  It expects
    that the setting of the low 32 bits always has the same meaning as a
    32-bit debugger setting those same 32 bits with native 32-bit
    facilities.
    
    This never arose before because the syscall restart check never
    matched any -ERESTART* values due to lack of sign extension.  Before
    that fix, even 32-bit ptrace setting orig_eax to -1 failed to trigger
    the restart check anyway.  So this was never noticed as a regression
    of 64-bit debuggers vs 32-bit debuggers on the same 64-bit kernel.
    
    Signed-off-by: Roland McGrath <roland@redhat.com>
    [ Changed to just do the sign-extension unconditionally on x86-64,
      since orig_ax is always just a small integer and doesn't need
      the full 64-bit range ]
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
    Roland McGrath authored Linus Torvalds committed

Mar 07, 2008

  1. bluetooth: Add another Broadcom device

    This adds another Broadcom BCM2045 based device to the blacklist, with
    these settings the micro dongle works on my system.
    
    Signed-off-by: Karsten Keil <kkeil@suse.de>
    Acked-by: Marcel Holtmann <marcel@holtmann.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
    Karsten Keil authored Linus Torvalds committed
  2. Merge branch 'slab-linus' of git://git.kernel.org/pub/scm/linux/kerne…

    …l/git/christoph/vm
    
    * 'slab-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/christoph/vm:
      slub: fix typo in Documentation/vm/slub.txt
      slab: NUMA slab allocator migration bugfix
      slub: Do not cross cacheline boundaries for very small objects
      slab - use angle brackets for include of kmalloc_sizes.h
      slab numa fallback logic: Do not pass unfiltered flags to page allocator
      slub statistics: Fix check for DEACTIVATE_REMOTE_FREES
    Linus Torvalds authored
  3. Merge git://git.kernel.org/pub/scm/linux/kernel/git/bart/ide-2.6

    * git://git.kernel.org/pub/scm/linux/kernel/git/bart/ide-2.6:
      ide: update references to Documentation/ide/ide.txt (v2)
      ide: move ide.txt to Documentation/ide/
      ide: fix buggy code in ide_register_hw()
      ide: fix enabling DMA on it821x in "smart" mode
      ide-cd: mark REQ_TYPE_ATA_PC write requests with REQ_RW flag
    Linus Torvalds authored
  4. ide: update references to Documentation/ide/ide.txt (v2)

    Fix all references to Documentation/ide/ide.txt.
    Add/update ide/00-INDEX file.
    
    Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
    Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
    Randy Dunlap authored bzolnier committed
  5. ide: move ide.txt to Documentation/ide/

    Cleanup some of Documentation directory:
    Move Documentation/ide.txt to the ide/ sub-directory.
    Fix trailing whitespace while there.
    
    Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
    Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
    Randy Dunlap authored bzolnier committed
  6. Peter Teoh

    ide: fix buggy code in ide_register_hw()

    Relocating the index to come after finding the hwif pointer.
    
    Signed-off-by: Peter Teoh <htmldeveloper@gmail.com>
    Reported-by: Adrian Bunk <bunk@kernel.org>
    Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
    tthtlc authored bzolnier committed
  7. bzolnier

    ide: fix enabling DMA on it821x in "smart" mode

    ide_tune_dma() should return '1' if IDE_HFLAG_NO_SET_MODE host flag is set.
    
    Cc: Sergei Shtylyov <sshtylyov@ru.mvista.com>
    Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
    bzolnier authored
  8. bzolnier

    ide-cd: mark REQ_TYPE_ATA_PC write requests with REQ_RW flag

    On Thursday 06 March 2008, walt wrote:
    
    > For me, this commit causes the problem it's intended to fix:
    > 
    > commit 9f10d9e
    > Author: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
    > Date:   Tue Feb 26 21:50:35 2008 +0100
    > 
    >      ide-cd: fix 'ireason' handling for REQ_TYPE_ATA_PC requests
    > 
    >      This fixes some hangs caused by not finishing the transfer before ending
    >      the request and also makes use of 'ireason == 1' quirk for spurious IRQs.
    > 
    > When I mount a CD there is a long delay, and I see this error message:
    > 
    > hdc: ide_cd_check_ireason: wrong transfer direction!
    > cdrom: failed setting lba address space
    > hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }
    > ide: failed opcode was: unknown
    > hdc: drive not ready for command
    > <repeated many times>
    > 
    > When I revert this commit everything works properly again, including
    > CD burning.
    
    It turned out that REQ_TYPE_ATA_PC write requests were not marked as such
    (the previous commit assumed them to be).
    
    Reported-by: walt <w41ter@gmail.com>
    Tested-by: walt <w41ter@gmail.com>
    Reviewed-by: Borislav Petkov <petkovbb@googlemail.com>
    Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
    bzolnier authored
  9. Merge branch 'hotfixes' of git://git.linux-nfs.org/projects/trondmy/n…

    …fs-2.6
    
    * 'hotfixes' of git://git.linux-nfs.org/projects/trondmy/nfs-2.6:
      NFS: Fix dentry revalidation for NFSv4 referrals and mountpoint crossings
      NFS: Fix the fsid revalidation in nfs_update_inode()
      SUNRPC: Fix a nfs4 over rdma transport oops
      NFS: Fix an f_mode/f_flags confusion in fs/nfs/write.c
    Linus Torvalds authored
  10. NFS: Fix dentry revalidation for NFSv4 referrals and mountpoint cross…

    …ings
    
    As long as the directory contents haven't changed, we should just let the
    path walk proceed to cross the mountpoint. Apart from being an optimisation
    in the case of 'nohide' mountpoint traversals, it also fixes an issue with
    referrals: referral inodes don't have valid filehandles, so calling
    nfs_revalidate_inode() on them is a bug.
    
    Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
    Trond Myklebust authored
  11. NFS: Fix the fsid revalidation in nfs_update_inode()

    When we detect that we've crossed a mountpoint on the remote server, we
    must take care not to use that inode to revalidate the fsid on our
    current superblock. To do so, we label the inode as a remote mountpoint,
    and check for that in nfs_update_inode().
    
    Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
    Trond Myklebust authored
  12. SUNRPC: Fix a nfs4 over rdma transport oops

    Prevent an RPC oops when freeing a dynamically allocated RDMA
    buffer, used in certain special-case large metadata operations.
    
    Signed-off-by: Tom Talpey <tmt@netapp.com>
    Signed-off-by: James Lentini <jlentini@netapp.com>
    Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
    Tom Talpey authored Trond Myklebust committed
  13. NFS: Fix an f_mode/f_flags confusion in fs/nfs/write.c

    O_SYNC is stored in filp->f_flags.
    Thanks to Al Viro for pointing out the bug.
    
    Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
    Trond Myklebust authored
  14. gigaset: fix Oops on module unload regression

    The card state mutex was only initialized when a device was connected,
    but used during unload unconditionally, leading to an Oops if a driver
    was loaded and unloaded again without ever connecting a device.
    
    Fix this by initializing the mutex as soon as the structure is allocated.
    Also add a missing mutex unlock revealed in the same execution path.
    
    This fixes a possible Oops in 2.6.25-rc that was introduced by commit
    e468c04 ("Gigaset: permit module
    unload").
    
    Thanks to Roland Kletzing for reporting this problem.
    
    Signed-off-by: Tilman Schmidt <tilman@imap.cc>
    Tested-by: Roland Kletzing <devzero@web.de>
    Cc: Hansjoerg Lipp <hjlipp@web.de>
    Cc: Karsten Keil <kkeil@suse.de>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
    Tilman Schmidt authored Linus Torvalds committed
  15. Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel…

    …/git/mingo/linux-2.6-sched-devel
    
    * 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/mingo/linux-2.6-sched-devel:
      sched: don't allow rt_runtime_us to be zero for groups having rt tasks
      sched: rt-group: fixup schedulability constraints calculation
      sched: fix the wrong time slice value for SCHED_FIFO tasks
      sched: export task_nice
      sched: balance RT task resched only on runqueue
      sched: retain vruntime
    Linus Torvalds authored
  16. Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel…

    …/git/x86/linux-2.6-x86
    
    * 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-x86:
      x86-boot: don't request VBE2 information
      x86: re-add reboot fixups
      x86: fix typo in step.c
      x86: fix merge mistake in i387.c
      x86: clear DF before calling signal handler
    Linus Torvalds authored
  17. drivers/char/esp.c: fix bootup lockup

    randconfig testing found a bootup lockup in drivers/char/esp.c because
    of a spinlock that wasn't correctly initialized.
    
    I'm not sure why it became more prominent in 2.6.25-rc4, the bug seems
    rather old and i've been doing allyesconfig bootups for ages with
    CONFIG_ESP enabled.
    
    This fixes this bootup lockup:
    
     PM: Adding info for No Bus:ttyP63
     ttyP32 at 0x0240 (irq = 0) is an ESP primary port
     BUG: spinlock lockup on CPU#0, swapper/1, f56dd004
     Pid: 1, comm: swapper Not tainted 2.6.25-rc4-sched-devel.git-x86-latest.git #402 [<c03ac6f4>] _raw_spin_lock+0x134/0x140
      [<c08649be>] _spin_lock_irqsave+0x5e/0x80
      [<c0b9fbfe>] ? espserial_init+0x2be/0x6e0
      [<c0b9fbfe>] espserial_init+0x2be/0x6e0
      [<c0b877a3>] kernel_init+0x83/0x260
      [<c0b9f940>] ? espserial_init+0x0/0x6e0
      [<c010416a>] ? restore_nocheck_notrace+0x0/0xe
      [<c0b87720>] ? kernel_init+0x0/0x260
      [<c0b87720>] ? kernel_init+0x0/0x260
      [<c0104507>] kernel_thread_helper+0x7/0x10
      =======================
    
    kzalloc() is not the way to initialize spinlocks anymore.
    
    Signed-off-by: Ingo Molnar <mingo@elte.hu>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
    Ingo Molnar authored Linus Torvalds committed
  18. sched: don't allow rt_runtime_us to be zero for groups having rt tasks

    This patch checks if we can set the rt_runtime_us to 0. If there is a
    realtime task in the group, we don't want to set the rt_runtime_us as 0
    or bad things will happen. (that task wont get any CPU time despite
    being TASK_RUNNNG)
    
    Signed-off-by: Dhaval Giani <dhaval@linux.vnet.ibm.com>
    Signed-off-by: Ingo Molnar <mingo@elte.hu>
    Dhaval Giani authored Ingo Molnar committed
  19. sched: rt-group: fixup schedulability constraints calculation

    it was only possible to configure the rt-group scheduling parameters
    beyond the default value in a very small range.
    
    that's because div64_64() has a different calling convention than
    do_div() :/
    
    fix a few untidies while we are here; sysctl_sched_rt_period may overflow
    due to that multiplication, so cast to u64 first. Also that RUNTIME_INF
    juggling makes little sense although its an effective NOP.
    
    Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
    Signed-off-by: Ingo Molnar <mingo@elte.hu>
    Peter Zijlstra authored Ingo Molnar committed
  20. Miao Xie

    sched: fix the wrong time slice value for SCHED_FIFO tasks

    Function sys_sched_rr_get_interval returns wrong time slice value for
    SCHED_FIFO tasks. The time slice for SCHED_FIFO tasks should be 0.
    
    Signed-off-by: Miao Xie <miaox@cn.fujitsu.com>
    Signed-off-by: Ingo Molnar <mingo@elte.hu>
    miaoxie authored Ingo Molnar committed
  21. Pavel Roskin

    sched: export task_nice

    The API is trivial, and so is the implementation.
    
    Signed-off-by: Pavel Roskin <proski@gnu.org>
    Signed-off-by: Ingo Molnar <mingo@elte.hu>
    proski authored Ingo Molnar committed
  22. Steven Rostedt

    sched: balance RT task resched only on runqueue

    Sripathi Kodi reported a crash in the -rt kernel:
    
      https://bugzilla.redhat.com/show_bug.cgi?id=435674
    
    this is due to a place that can reschedule a task without holding
    the tasks runqueue lock.  This was caused by the RT balancing code
    that pulls RT tasks to the current run queue and will reschedule the
    current task.
    
    There's a slight chance that the pulling of the RT tasks will release
    the current runqueue's lock and retake it (in the double_lock_balance).
    During this time that the runqueue is released, the current task can
    migrate to another runqueue.
    
    In the prio_changed_rt code, after the pull, if the current task is of
    lesser priority than one of the RT tasks pulled, resched_task is called
    on the current task. If the current task had migrated in that small
    window, resched_task will be called without holding the runqueue lock
    for the runqueue that the task is on.
    
    This race condition also exists in the mainline kernel and this patch
    adds a check to make sure the task hasn't migrated before calling
    resched_task.
    
    Signed-off-by: Steven Rostedt <srostedt@redhat.com>
    Tested-by: Sripathi Kodi <sripathik@in.ibm.com>
    Acked-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
    Signed-off-by: Ingo Molnar <mingo@elte.hu>
    rostedt authored Ingo Molnar committed
Something went wrong with that request. Please try again.