Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
tag: v2.6.33-rc8-gi…
Commits on Feb 16, 2010
  1. @torvalds

    Merge git://git.kernel.org/pub/scm/linux/kernel/git/agk/linux-2.6-dm

    torvalds authored
    * git://git.kernel.org/pub/scm/linux/kernel/git/agk/linux-2.6-dm:
      dm: sysfs revert add empty release function to avoid debug warning
      dm mpath: fix stall when requeueing io
      dm raid1: fix null pointer dereference in suspend
      dm raid1: fail writes if errors are not handled and log fails
      dm log: userspace fix overhead_size calcuations
      dm snapshot: persistent annotate work_queue as on stack
      dm stripe: avoid divide by zero with invalid stripe count
  2. @torvalds

    Merge branch 'release' of git://git.kernel.org/pub/scm/linux/kernel/g…

    torvalds authored
    …it/aegl/linux-2.6
    
    * 'release' of git://git.kernel.org/pub/scm/linux/kernel/git/aegl/linux-2.6:
      [IA64] preserve personality flag bits across exec
  3. dm: sysfs revert add empty release function to avoid debug warning

    Alasdair G Kergon authored
    Revert commit d2bb7df at Greg's request.
    
        Author: Milan Broz <mbroz@redhat.com>
        Date:   Thu Dec 10 23:51:53 2009 +0000
    
        dm: sysfs add empty release function to avoid debug warning
    
        This patch just removes an unnecessary warning:
         kobject: 'dm': does not have a release() function,
         it is broken and must be fixed.
    
        The kobject is embedded in mapped device struct, so
        code does not need to release memory explicitly here.
    
    Cc: Greg KH <gregkh@suse.de>
    Signed-off-by: Alasdair G Kergon <agk@redhat.com>
  4. dm mpath: fix stall when requeueing io

    Kiyoshi Ueda authored Alasdair G Kergon committed
    This patch fixes the problem that system may stall if target's ->map_rq
    returns DM_MAPIO_REQUEUE in map_request().
    E.g. stall happens on 1 CPU box when a dm-mpath device with queue_if_no_path
         bounces between all-paths-down and paths-up on I/O load.
    
    When target's ->map_rq returns DM_MAPIO_REQUEUE, map_request() requeues
    the request and returns to dm_request_fn().  Then, dm_request_fn()
    doesn't exit the I/O dispatching loop and continues processing
    the requeued request again.
    This map and requeue loop can be done with interrupt disabled,
    so 1 CPU system can be stalled if this situation happens.
    
    For example, commands below can stall my 1 CPU box within 1 minute or so:
      # dmsetup table mp
      mp: 0 2097152 multipath 1 queue_if_no_path 0 1 1 service-time 0 1 2 8:144 1 1
      # while true; do dd if=/dev/mapper/mp of=/dev/null bs=1M count=100; done &
      # while true; do \
      > dmsetup message mp 0 "fail_path 8:144" \
      > dmsetup suspend --noflush mp \
      > dmsetup resume mp \
      > dmsetup message mp 0 "reinstate_path 8:144" \
      > done
    
    To fix the problem above, this patch changes dm_request_fn() to exit
    the I/O dispatching loop once if a request is requeued in map_request().
    
    Signed-off-by: Kiyoshi Ueda <k-ueda@ct.jp.nec.com>
    Signed-off-by: Jun'ichi Nomura <j-nomura@ce.jp.nec.com>
    Cc: stable@kernel.org
    Signed-off-by: Alasdair G Kergon <agk@redhat.com>
  5. dm raid1: fix null pointer dereference in suspend

    Takahiro Yasui authored Alasdair G Kergon committed
    When suspending a failed mirror, bios are completed by mirror_end_io() and
    __rh_lookup() in dm_rh_dec() returns NULL where a non-NULL return value is
    required by design.  Fix this by not changing the state of the recovery failed
    region from DM_RH_RECOVERING to DM_RH_NOSYNC in dm_rh_recovery_end().
    
    Issue
    
    On 2.6.33-rc1 kernel, I hit the bug when I suspended the failed
    mirror by dmsetup command.
    
    BUG: unable to handle kernel NULL pointer dereference at 00000020
    IP: [<f94f38e2>] dm_rh_dec+0x35/0xa1 [dm_region_hash]
    ...
    EIP: 0060:[<f94f38e2>] EFLAGS: 00010046 CPU: 0
    EIP is at dm_rh_dec+0x35/0xa1 [dm_region_hash]
    EAX: 00000286 EBX: 00000000 ECX: 00000286 EDX: 00000000
    ESI: eff79eac EDI: eff79e80 EBP: f6915cd4 ESP: f6915cc4
     DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
    Process dmsetup (pid: 2849, ti=f6914000 task=eff03e80 task.ti=f6914000)
     ...
    Call Trace:
     [<f9530af6>] ? mirror_end_io+0x53/0x1b1 [dm_mirror]
     [<f9413104>] ? clone_endio+0x4d/0xa2 [dm_mod]
     [<f9530aa3>] ? mirror_end_io+0x0/0x1b1 [dm_mirror]
     [<f94130b7>] ? clone_endio+0x0/0xa2 [dm_mod]
     [<c02d6bcb>] ? bio_endio+0x28/0x2b
     [<f952f303>] ? hold_bio+0x2d/0x62 [dm_mirror]
     [<f952f942>] ? mirror_presuspend+0xeb/0xf7 [dm_mirror]
     [<c02aa3e2>] ? vmap_page_range+0xb/0xd
     [<f9414c8d>] ? suspend_targets+0x2d/0x3b [dm_mod]
     [<f9414ca9>] ? dm_table_presuspend_targets+0xe/0x10 [dm_mod]
     [<f941456f>] ? dm_suspend+0x4d/0x150 [dm_mod]
     [<f941767d>] ? dev_suspend+0x55/0x18a [dm_mod]
     [<c0343762>] ? _copy_from_user+0x42/0x56
     [<f9417fb0>] ? dm_ctl_ioctl+0x22c/0x281 [dm_mod]
     [<f9417628>] ? dev_suspend+0x0/0x18a [dm_mod]
     [<f9417d84>] ? dm_ctl_ioctl+0x0/0x281 [dm_mod]
     [<c02c3c4b>] ? vfs_ioctl+0x22/0x85
     [<c02c422c>] ? do_vfs_ioctl+0x4cb/0x516
     [<c02c42b7>] ? sys_ioctl+0x40/0x5a
     [<c0202858>] ? sysenter_do_call+0x12/0x28
    
    Analysis
    
    When recovery process of a region failed, dm_rh_recovery_end() function
    changes the state of the region from RM_RH_RECOVERING to DM_RH_NOSYNC.
    When recovery_complete() is executed between dm_rh_update_states() and
    dm_writes() in do_mirror(), bios are processed with the region state,
    DM_RH_NOSYNC. However, the region data is freed without checking its
    pending count when dm_rh_update_states() is called next time.
    
    When bios are finished by mirror_end_io(), __rh_lookup() in dm_rh_dec()
    returns NULL even though a valid return value are expected.
    
    Solution
    
    Remove the state change of the recovery failed region from DM_RH_RECOVERING
    to DM_RH_NOSYNC in dm_rh_recovery_end(). We can remove the state change
    because:
    
      - If the region data has been released by dm_rh_update_states(),
        a new region data is created with the state of DM_RH_NOSYNC, and
        bios are processed according to the DM_RH_NOSYNC state.
    
      - If the region data has not been released by dm_rh_update_states(),
        a state of the region is DM_RH_RECOVERING and bios are put in the
        delayed_bio list.
    
    The flag change from DM_RH_RECOVERING to DM_RH_NOSYNC in dm_rh_recovery_end()
    was added in the following commit:
      dm raid1: handle resync failures
      author  Jonathan Brassow <jbrassow@redhat.com>
        Thu, 12 Jul 2007 16:29:04 +0000 (17:29 +0100)
      http://git.kernel.org/linus/f44db678edcc6f4c2779ac43f63f0b9dfa28b724
    
    Signed-off-by: Takahiro Yasui <tyasui@redhat.com>
    Reviewed-by: Mikulas Patocka <mpatocka@redhat.com>
    Signed-off-by: Alasdair G Kergon <agk@redhat.com>
  6. dm raid1: fail writes if errors are not handled and log fails

    Mikulas Patocka authored Alasdair G Kergon committed
    If the mirror log fails when the handle_errors option was not selected
    and there is no remaining valid mirror leg, writes return success even
    though they weren't actually written to any device.  This patch
    completes them with EIO instead.
    
    This code path is taken:
    do_writes:
    	bio_list_merge(&ms->failures, &sync);
    do_failures:
    	if (!get_valid_mirror(ms)) (false)
    	else if (errors_handled(ms)) (false)
    	else bio_endio(bio, 0);
    
    The logic in do_failures is based on presuming that the write was already
    tried: if it succeeded at least on one leg (without handle_errors) it
    is reported as success.
    
    Reference: https://bugzilla.redhat.com/show_bug.cgi?id=555197
    
    Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
    Signed-off-by: Alasdair G Kergon <agk@redhat.com>
  7. @jbrassow

    dm log: userspace fix overhead_size calcuations

    jbrassow authored Alasdair G Kergon committed
    This patch fixes two bugs that revolve around the miscalculation and
    misuse of the variable 'overhead_size'.  'overhead_size' is the size of
    the various header structures used during communication.
    
    The first bug is the use of 'sizeof' with the pointer of a structure
    instead of the structure itself - resulting in the wrong size being
    computed.  This is then used in a check to see if the payload
    (data_size) would be to large for the preallocated structure.  Since the
    bug produces a smaller value for the overhead, it was possible for the
    structure to be breached.  (Although the current users of the code do
    not currently send enough data to trigger this bug.)
    
    The second bug is that the 'overhead_size' value is used to compute how
    much of the preallocated space should be cleared before populating it
    with fresh data.  This should have simply been 'sizeof(struct cn_msg)'
    not overhead_size.  The fact that 'overhead_size' was computed
    incorrectly made this problem "less bad" - leaving only a pointer's
    worth of space at the end uncleared.  Thus, this bug was never producing
    a bad result, but still needs to be fixed - especially now that the
    value is computed correctly.
    
    Cc: stable@kernel.org
    Signed-off-by: Jonathan Brassow <jbrassow@redhat.com
    Signed-off-by: Alasdair G Kergon <agk@redhat.com>
  8. @snitm

    dm snapshot: persistent annotate work_queue as on stack

    snitm authored Alasdair G Kergon committed
    chunk_io() declares its 'struct mdata_req' on the stack and then
    initializes its 'struct work_struct' member.  Annotate the
    initialization of this workqueue with INIT_WORK_ON_STACK to suppress a
    debugobjects warning seen when CONFIG_DEBUG_OBJECTS_WORK is enabled.
    
    Signed-off-by: Mike Snitzer <snitzer@redhat.com>
    Signed-off-by: Alasdair G Kergon <agk@redhat.com>
  9. dm stripe: avoid divide by zero with invalid stripe count

    Nikanth Karthikesan authored Alasdair G Kergon committed
    If a table containing zero as stripe count is passed into stripe_ctr
    the code attempts to divide by zero.
    
    This patch changes DM_TABLE_LOAD to return -EINVAL if the stripe count
    is zero.
    
    We now get the following error messages:
      device-mapper: table: 253:0: striped: Invalid stripe count
      device-mapper: ioctl: error adding target to table
    
    Signed-off-by: Nikanth Karthikesan <knikanth@suse.de>
    Cc: stable@kernel.org
    Signed-off-by: Alasdair G Kergon <agk@redhat.com>
  10. @utrace @torvalds

    x86: ELF_PLAT_INIT() shouldn't worry about TIF_IA32

    utrace authored torvalds committed
    The 64-bit version of ELF_PLAT_INIT() clears TIF_IA32, but at this point
    it has already been cleared by SET_PERSONALITY == set_personality_64bit.
    
    Signed-off-by: Oleg Nesterov <oleg@redhat.com>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
  11. @utrace @torvalds

    x86: set_personality_ia32() misses force_personality32

    utrace authored torvalds committed
    05d43ed "x86: get rid of the insane TIF_ABI_PENDING bit" forgot about
    force_personality32.  Fix.
    
    Signed-off-by: Oleg Nesterov <oleg@redhat.com>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
  12. @torvalds

    Merge git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-unstable

    torvalds authored
    * git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-unstable:
      Btrfs: btrfs_mark_extent_written uses the wrong slot
  13. @torvalds

    Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel…

    torvalds authored
    …/git/ieee1394/linux1394-2.6
    
    * 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394-2.6:
      firewire: ohci: retransmit isochronous transmit packets on cycle loss
      firewire: net: fix panic in fwnet_write_complete
  14. @torvalds

    Merge branch 'fix/hda' of git://git.kernel.org/pub/scm/linux/kernel/g…

    torvalds authored
    …it/tiwai/sound-2.6
    
    * 'fix/hda' of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-2.6:
      ALSA: hda - Correct ASUA blacklist for MSI brokenness
  15. @chucklever @torvalds

    NFS: Too many GETATTR and ACCESS calls after direct I/O

    chucklever authored torvalds committed
    The cached read and write paths initialize fattr->time_start in their
    setup procedures.  The value of fattr->time_start is propagated to
    read_cache_jiffies by nfs_update_inode().  Subsequent calls to
    nfs_attribute_timeout() will then use a good time stamp when
    computing the attribute cache timeout, and squelch unneeded GETATTR
    calls.
    
    Since the direct I/O paths erroneously leave the inode's
    fattr->time_start field set to zero, read_cache_jiffies for that inode
    is set to zero after any direct read or write operation.  This
    triggers an otw GETATTR or ACCESS call to update the file's attribute
    and access caches properly, even when the NFS READ or WRITE replies
    have usable post-op attributes.
    
    Make sure the direct read and write setup code performs the same fattr
    initialization as the cached I/O paths to prevent unnecessary GETATTR
    calls.
    
    This was likely introduced by commit 0e574af in 2.6.15, which appears
    to add new nfs_fattr_init() call sites in the cached read and write
    paths, but not in the equivalent places in fs/nfs/direct.c.  A
    subsequent commit in the same series, 3380114, introduces the
    fattr->time_start field.
    
    Interestingly, the direct write reschedule path already has a call to
    nfs_fattr_init() in the right place.
    
    Reported-by: Quentin Barnes <qbarnes@yahoo-inc.com>
    Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
    Cc: stable@kernel.org
    Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
  16. @torvalds

    Merge branch 'timers-fixes-for-linus' of git://git.kernel.org/pub/scm…

    torvalds authored
    …/linux/kernel/git/tip/linux-2.6-tip
    
    * 'timers-fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip:
      hrtimer, softirq: Fix hrtimer->softirq trampoline
  17. @torvalds

    Merge branch 'reiserfs/kill-bkl' of git://git.kernel.org/pub/scm/linu…

    torvalds authored
    …x/kernel/git/frederic/random-tracing
    
    * 'reiserfs/kill-bkl' of git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing:
      reiserfs: Fix softlockup while waiting on an inode
  18. @torvalds

    Merge branch 'drm-linus' of git://git.kernel.org/pub/scm/linux/kernel…

    torvalds authored
    …/git/airlied/drm-2.6
    
    * 'drm-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6:
      drm/radeon/kms: make sure retry count increases.
      drm/radeon/kms/atom: use get_unaligned_le32() for ctx->ps
      drm/ttm: Fix a bug occuring when validating a buffer object in a range.
      drm: Fix a bug in the range manager.
  19. @torvalds

    Merge branch 'sh/for-2.6.33' of git://git.kernel.org/pub/scm/linux/ke…

    torvalds authored
    …rnel/git/lethal/sh-2.6
    
    * 'sh/for-2.6.33' of git://git.kernel.org/pub/scm/linux/kernel/git/lethal/sh-2.6:
      sh64: fix tracing of signals.
  20. @torvalds

    Merge branch 'tracing-fixes-for-linus' of git://git.kernel.org/pub/sc…

    torvalds authored
    …m/linux/kernel/git/tip/linux-2.6-tip
    
    * 'tracing-fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip:
      tracing/kprobes: Fix probe parsing
      tracing: Fix circular dead lock in stack trace
  21. @torvalds

    Merge branch 'perf-fixes-for-linus' of git://git.kernel.org/pub/scm/l…

    torvalds authored
    …inux/kernel/git/tip/linux-2.6-tip
    
    * 'perf-fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip:
      perf top: Fix help text alignment
      perf: Fix hypervisor sample reporting
      perf: Make bp_len type to u64 generic across the arch
Commits on Feb 15, 2010
  1. @tiwai

    ALSA: hda - Correct ASUA blacklist for MSI brokenness

    tiwai authored
    The MSI blacklist entry for ASUS mobo added in the commit
    8ce28d6 was based on the alsa-info
    output wrongly posted.  Fix the id to the right one now.
    
    Reported-by: Sid Boyce <sboyce@blueyonder.co.uk>
    Signed-off-by: Takashi Iwai <tiwai@suse.de>
  2. drm/radeon/kms: make sure retry count increases.

    Dave Airlie authored
    In testing I've never seen it go past 1 retry anyways but better
    safe than sorry.
    
    Reported by Droste on irc.
    
    Signed-off-by: Dave Airlie <airlied@redhat.com>
  3. @pmundt

    sh64: fix tracing of signals.

    pmundt authored
    This follows the parisc change to ensure that tracehook_signal_handler()
    is aware of when we are single-stepping in order to ptrace_notify()
    appropriately. While this was implemented for 32-bit SH, sh64 neglected
    to make use of TIF_SINGLESTEP when it was folded in with the 32-bit code,
    resulting in ptrace_notify() never being called.
    
    As sh64 uses all of the other abstractions already, this simply plugs in
    the thread flag in the appropriate enable/disable paths and fixes up the
    tracehook notification accordingly. With this in place, sh64 is brought
    in line with what 32-bit is already doing.
    
    Reported-by: Mike Frysinger <vapier@gentoo.org>
    Signed-off-by: Paul Mundt <lethal@linux-sh.org>
  4. @mattst88

    drm/radeon/kms/atom: use get_unaligned_le32() for ctx->ps

    mattst88 authored Dave Airlie committed
    Noticed on a DEC Alpha.
    
    Start up into console mode caused 15 unaligned accesses, and starting X
    caused another 48.
    
    Signed-off-by: Matt Turner <mattst88@gmail.com>
    CC: Jerome Glisse <jglisse@redhat.com>
    CC: Alex Deucher <alexdeucher@gmail.com>
    Signed-off-by: Dave Airlie <airlied@redhat.com>
  5. drm/ttm: Fix a bug occuring when validating a buffer object in a range.

    Thomas Hellstrom authored Dave Airlie committed
    If the buffer object was already in the requested memory type, but
    outside of the requested range it was never moved into the requested range.
    
    Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com>
    Signed-off-by: Dave Airlie <airlied@redhat.com>
  6. drm: Fix a bug in the range manager.

    Thomas Hellstrom authored Dave Airlie committed
    When searching for free space in a range, the function could return a node extending outside of the given range.
    
    Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com>
    Signed-off-by: Dave Airlie <airlied@redhat.com>
Commits on Feb 14, 2010
  1. @fweisbec

    reiserfs: Fix softlockup while waiting on an inode

    fweisbec authored
    When we wait for an inode through reiserfs_iget(), we hold
    the reiserfs lock. And waiting for an inode may imply waiting
    for its writeback. But the inode writeback path may also require
    the reiserfs lock, which leads to a deadlock.
    
    We just need to release the reiserfs lock from reiserfs_iget()
    to fix this.
    
    Reported-by: Alexander Beregalov <a.beregalov@gmail.com>
    Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>
    Tested-by: Christian Kujau <lists@nerdbynature.de>
    Cc: Chris Mason <chris.mason@oracle.com>
  2. @cladisch

    firewire: ohci: retransmit isochronous transmit packets on cycle loss

    cladisch authored Stefan Richter committed
    In isochronous transmit DMA descriptors, link the skip address pointer
    back to the descriptor itself.  When a cycle is lost, the controller
    will send the packet in the next cycle, instead of terminating the
    entire DMA program.
    
    There are two reasons for this:
    
    * This behaviour is compatible with the old IEEE1394 stack.  Old
      applications would not expect the DMA program to stop in this case.
    
    * Since the OHCI driver does not report any uncompleted packets, the
      context would stop silently; clients would not have any chance to
      detect and handle this error without a watchdog timer.
    
    Signed-off-by: Clemens Ladisch <clemens@ladisch.de>
    
    Pieter Palmers notes:
    
    "The reason I added this retry behavior to the old stack is because some
    cards now and then fail to send a packet (e.g. the o2micro card in my
    dell laptop).  I couldn't figure out why exactly this happens, my best
    guess is that the card cannot fetch the payload data on time.  This
    happens much more frequently when sending large packets, which leads me
    to suspect that there are some contention issues with the DMA that fills
    the transmit FIFO.
    
    In the old stack it was a pretty critical issue as it resulted in a
    freeze of the userspace application.
    
    The omission of a packet doesn't necessarily have to be an issue.  E.g.
    in IEC61883 streams the DBC field can be used to detect discontinuities
    in the stream.  So as long as the other side doesn't bail when no
    [packet] is present in a cycle, there is not really a problem.
    
    I'm not convinced though that retrying is the proper solution, but it is
    simple and effective for what it had to do.  And I think there are no
    reasons not to do it this way.  Userspace can still detect this by
    checking the cycle the descriptor was sent in."
    
    Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de> (changelog, comment)
  3. perf top: Fix help text alignment

    Kirill Smelkov authored Ingo Molnar committed
    Print this:
    
    Mapped keys:
            [d]     display refresh delay.                  (2)
            [e]     display entries (lines).                (46)
            [f]     profile display filter (count).         (5)
            [F]     annotate display filter (percent).      (5%)
            [s]     annotate symbol.                        (NULL)
            [S]     stop annotation.
            [K]     hide kernel_symbols symbols.            (no)
            [U]     hide user symbols.                      (no)
            [z]     toggle sample zeroing.                  (0)
            [qQ]    quit.
    
    instead of:
    
    Mapped keys:
            [d]     display refresh delay.                  (2)
            [e]     display entries (lines).                (46)
            [f]     profile display filter (count).         (5)
            [F]     annotate display filter (percent).      (5%)
            [s]     annotate symbol.                        (NULL)
            [S]     stop annotation.
            [K]     hide kernel_symbols symbols.                    (no)
            [U]     hide user symbols.                      (no)
            [z]     toggle sample zeroing.                  (0)
            [qQ]    quit.
    
    Signed-off-by: Kirill Smelkov <kirr@landau.phys.spbu.ru>
    Acked-by: Arnaldo Carvalho de Melo <acme@redhat.com>
    Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
    Cc: Mike Galbraith <efault@gmx.de>
    Cc: Paul Mackerras <paulus@samba.org>
    Cc: Frederic Weisbecker <fweisbec@gmail.com>
    LKML-Reference: <20100212162059.GA30041@landau.phys.spbu.ru>
    Signed-off-by: Ingo Molnar <mingo@elte.hu>
  4. tracing/kprobes: Fix probe parsing

    Heiko Carstens authored Ingo Molnar committed
    Trying to add a probe like:
    
      echo p:myprobe 0x10000 > /sys/kernel/debug/tracing/kprobe_events
    
    will fail since the wrong pointer is passed to strict_strtoul
    when trying to convert the address to an unsigned long.
    
    Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>
    Acked-by: Masami Hiramatsu <mhiramat@redhat.com>
    Cc: Frederic Weisbecker <fweisbec@gmail.com>
    Cc: Steven Rostedt <rostedt@goodmis.org>
    LKML-Reference: <20100210162346.GA6933@osiris.boeblingen.de.ibm.com>
    Signed-off-by: Ingo Molnar <mingo@elte.hu>
Commits on Feb 12, 2010
  1. @chrismason-xx

    Btrfs: btrfs_mark_extent_written uses the wrong slot

    Shaohua Li authored chrismason-xx committed
    My test do: fallocate a big file and do write. The file is 512M, but
    after file write is done btrfs-debug-tree shows:
    item 6 key (257 EXTENT_DATA 0) itemoff 3516 itemsize 53
                    extent data disk byte 1103101952 nr 536870912
                    extent data offset 0 nr 399634432 ram 536870912
                    extent compression 0
    Looks like a regression introducted by
    6c7d54a, where we set wrong slot.
    
    Signed-off-by: Shaohua Li <shaohua.li@intel.com>
    Acked-by: Yan Zheng <zheng.yan@oracle.com>
    Signed-off-by: Chris Mason <chris.mason@oracle.com>
  2. @torvalds

    Linux 2.6.33-rc8

    torvalds authored
  3. @torvalds

    Merge branch 'fix/hda' of git://git.kernel.org/pub/scm/linux/kernel/g…

    torvalds authored
    …it/tiwai/sound-2.6
    
    * 'fix/hda' of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-2.6:
      ALSA: hda - use WARN_ON_ONCE() for zero-division detection
  4. @torvalds

    Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel…

    torvalds authored
    …/git/anholt/drm-intel
    
    * 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/anholt/drm-intel:
      drm/i915: hold ref on flip object until it completes
      drm/i915: Fix crash while aborting hibernation
      drm/i915: Correctly return -ENOMEM on allocation failure in cmdbuf ioctls.
      drm/i915: fix pipe source image setting in flip command
      drm/i915: fix flip done interrupt on Ironlake
      drm/i915: untangle page flip completion
      drm/i915: handle FBC and self-refresh better
      drm/i915: Increase fb alignment to 64k
      drm/i915: Update write_domains on active list after flush.
      drm/i915: Rework DPLL calculation parameters for Ironlake
Something went wrong with that request. Please try again.