Permalink
Commits on Oct 8, 2012
  1. Merge branch 'ck-3.6' into pf-3.6

    Oleksandr Natalenko
    Oleksandr Natalenko committed Oct 8, 2012
  2. ck-3.6: remove extra version info

    Oleksandr Natalenko
    Oleksandr Natalenko committed Oct 8, 2012
  3. Merge branch 'configs-3.6' into pf-3.6

    Oleksandr Natalenko
    Oleksandr Natalenko committed Oct 8, 2012
  4. configs-3.6: update dell-vostro-3360.config

    Oleksandr Natalenko
    Oleksandr Natalenko committed Oct 8, 2012
  5. Merge branch 'distro-3.6' into pf-3.6

    Oleksandr Natalenko
    Oleksandr Natalenko committed Oct 8, 2012
  6. Merge branch 'version-3.6' into pf-3.6

    Oleksandr Natalenko
    Oleksandr Natalenko committed Oct 8, 2012
  7. distro-3.6: bump to v3.6.2-pf

    Oleksandr Natalenko
    Oleksandr Natalenko committed Oct 8, 2012
  8. version-3.6: bump to v3.6.2-pf

    Oleksandr Natalenko
    Oleksandr Natalenko committed Oct 8, 2012
  9. Merge branch 'ck-3.6' into pf-3.6

    Oleksandr Natalenko
    Oleksandr Natalenko committed Oct 8, 2012
  10. Revert "Merge branch 'bfs-3.6' into pf-3.6"

    Oleksandr Natalenko
    Oleksandr Natalenko committed Oct 8, 2012
    This reverts commit d7a3470, reversing
    changes made to b7d3337.
  11. Revert "Merge branch 'bfs-3.6' into pf-3.6"

    Oleksandr Natalenko
    Oleksandr Natalenko committed Oct 8, 2012
    This reverts commit 71cf16a, reversing
    changes made to d8f971a.
  12. Revert "Merge branch 'bfs-3.6' into pf-3.6"

    Oleksandr Natalenko
    Oleksandr Natalenko committed Oct 8, 2012
    This reverts commit 4a685fd, reversing
    changes made to ac07646.
  13. Merge branch 'bfs-3.6' into pf-3.6

    Oleksandr Natalenko
    Oleksandr Natalenko committed Oct 8, 2012
  14. ck-3.6: cleanup

    Oleksandr Natalenko
    Oleksandr Natalenko committed Oct 8, 2012
  15. ck-3.6: add ported -ck patchset for 3.6 kernel

    Oleksandr Natalenko
    Oleksandr Natalenko committed Oct 8, 2012
  16. bfs-3.6: update BFSv424

    Oleksandr Natalenko
    Oleksandr Natalenko committed Oct 8, 2012
Commits on Oct 7, 2012
  1. fix merge conflict

    Oleksandr Natalenko
    Oleksandr Natalenko committed Oct 7, 2012
  2. Linux 3.6.1

    gregkh committed Oct 7, 2012
  3. SCSI: scsi_dh_alua: Enable STPG for unavailable ports

    bvanassche authored and gregkh committed Aug 24, 2012
    commit e47f897 upstream.
    
    A quote from SPC-4: "While in the unavailable primary target port
    asymmetric access state, the device server shall support those of
    the following commands that it supports while in the active/optimized
    state: [ ... ] d) SET TARGET PORT GROUPS; [ ... ]". Hence enable
    sending STPG to a target port group that is in the unavailable state.
    
    Signed-off-by: Bart Van Assche <bvanassche@acm.org>
    Reviewed-by: Mike Christie <michaelc@cs.wisc.edu>
    Acked-by: Hannes Reinecke <hare@suse.de>
    Signed-off-by: James Bottomley <JBottomley@Parallels.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  4. SCSI: scsi_remove_target: fix softlockup regression on hot remove

    Dan Williams authored and gregkh committed Aug 29, 2012
    commit bc3f02a upstream.
    
    John reports:
     BUG: soft lockup - CPU#2 stuck for 23s! [kworker/u:8:2202]
     [..]
     Call Trace:
      [<ffffffff8141782a>] scsi_remove_target+0xda/0x1f0
      [<ffffffff81421de5>] sas_rphy_remove+0x55/0x60
      [<ffffffff81421e01>] sas_rphy_delete+0x11/0x20
      [<ffffffff81421e35>] sas_port_delete+0x25/0x160
      [<ffffffff814549a3>] mptsas_del_end_device+0x183/0x270
    
    ...introduced by commit 3b661a9 "[SCSI] fix hot unplug vs async scan race".
    
    Don't restart lookup of more stargets in the multi-target case, just
    arrange to traverse the list once, on the assumption that new targets
    are always added at the end.  There is no guarantee that the target will
    change state in scsi_target_reap() so we can end up spinning if we
    restart.
    
    Acked-by: Jack Wang <jack_wang@usish.com>
    LKML-Reference: <CAEhu1-6wq1YsNiscGMwP4ud0Q+MrViRzv=kcWCQSBNc8c68N5Q@mail.gmail.com>
    Reported-by: John Drescher <drescherjm@gmail.com>
    Tested-by: John Drescher <drescherjm@gmail.com>
    Signed-off-by: Dan Williams <djbw@fb.com>
    Signed-off-by: James Bottomley <JBottomley@Parallels.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  5. isci: fix isci_pci_probe() generates warning on efi failure path

    djbw authored and gregkh committed Jun 22, 2012
    commit 6d70a74 upstream.
    
    The oem parameter image embedded in the efi variable is at an offset
    from the start of the variable.  However, in the failure path we try to
    free the 'orom' pointer which is only valid when the paramaters are
    being read from the legacy option-rom space.
    
    Since failure to load the oem parameters is unlikely and we keep the
    memory around in the success case just defer all de-allocation to devm.
    
    Reported-by: Don Morris <don.morris@hp.com>
    Signed-off-by: Dan Williams <dan.j.williams@intel.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  6. IB/qib: Fix local access validation for user MRs

    mmarcini authored and gregkh committed Sep 28, 2012
    commit c00aaa1 upstream.
    
    Commit 8aac4cc ("IB/qib: RCU locking for MR validation") introduced
    a bug that broke user post sends.  The proper validation of the MR
    was lost in the patch.
    
    This patch corrects that validation.
    
    Reviewed-by: Dean Luick <dean.luick@intel.com>
    Signed-off-by: Mike Marciniszyn <mike.marciniszyn@intel.com>
    Signed-off-by: Roland Dreier <roland@purestorage.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  7. IB/srp: Avoid having aborted requests hang

    bvanassche authored and gregkh committed Aug 24, 2012
    commit d853667 upstream.
    
    We need to call scsi_done() for commands after we abort them.
    
    Signed-off-by: Bart Van Assche <bvanassche@acm.org>
    Acked-by: David Dillow <dillowda@ornl.gov>
    Signed-off-by: Roland Dreier <roland@purestorage.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  8. IB/srp: Fix use-after-free in srp_reset_req()

    bvanassche authored and gregkh committed Aug 24, 2012
    commit 9b796d0 upstream.
    
    srp_free_req() uses the scsi_cmnd structure contents to unmap
    buffers, so we must invoke srp_free_req() before we release
    ownership of that structure.
    
    Signed-off-by: Bart Van Assche <bvanassche@acm.org>
    Acked-by: David Dillow <dillowda@ornl.gov>
    Signed-off-by: Roland Dreier <roland@purestorage.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  9. IPoIB: Fix use-after-free of multicast object

    kaber authored and gregkh committed Aug 30, 2012
    commit bea1e22 upstream.
    
    Fix a crash in ipoib_mcast_join_task().  (with help from Or Gerlitz)
    
    Commit c8c2afe ("IPoIB: Use rtnl lock/unlock when changing device
    flags") added a call to rtnl_lock() in ipoib_mcast_join_task(), which
    is run from the ipoib_workqueue, and hence the workqueue can't be
    flushed from the context of ipoib_stop().
    
    In the current code, ipoib_stop() (which doesn't flush the workqueue)
    calls ipoib_mcast_dev_flush(), which goes and deletes all the
    multicast entries.  This takes place without any synchronization with
    a possible running instance of ipoib_mcast_join_task() for the same
    ipoib device, leading to a crash due to NULL pointer dereference.
    
    Fix this by making sure that the workqueue is flushed before
    ipoib_mcast_dev_flush() is called.  To make that possible, we move the
    RTNL-lock wrapped code to ipoib_mcast_join_finish().
    
    Signed-off-by: Patrick McHardy <kaber@trash.net>
    Signed-off-by: Roland Dreier <roland@purestorage.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  10. remoteproc: fix a potential NULL-dereference on cleanup

    Dan Carpenter authored and gregkh committed Sep 25, 2012
    commit 7168d91 upstream.
    
    We only need to allocate mapping if there is an IOMMU domain.
    
    Otherwise, when the mappings are released, the assumption that
    an IOMMU domain is there will crash and burn.
    
    Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
    [ohad: revise commit log]
    Signed-off-by: Ohad Ben-Cohen <ohad@wizery.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  11. remoteproc: select VIRTIO to avoid build breakage

    ohadbc authored and gregkh committed Sep 30, 2012
    commit 2ed6d29 upstream.
    
    drivers/built-in.o: In function `rproc_virtio_finalize_features':
    remoteproc_virtio.c:(.text+0x2f9a02): undefined reference to `vring_transport_features'
    drivers/built-in.o: In function `rproc_virtio_del_vqs':
    remoteproc_virtio.c:(.text+0x2f9a74): undefined reference to `vring_del_virtqueue'
    drivers/built-in.o: In function `rproc_virtio_find_vqs':
    remoteproc_virtio.c:(.text+0x2f9c44): undefined reference to `vring_new_virtqueue'
    drivers/built-in.o: In function `rproc_add_virtio_dev':
    (.text+0x2f9e2c): undefined reference to `register_virtio_device'
    drivers/built-in.o: In function `rproc_vq_interrupt':
    (.text+0x2f9db7): undefined reference to `vring_interrupt'
    drivers/built-in.o: In function `rproc_remove_virtio_dev':
    (.text+0x2f9e9f): undefined reference to `unregister_virtio_device'
    
    Reported-by: Randy Dunlap <rdunlap@xenotime.net>
    Signed-off-by: Ohad Ben-Cohen <ohad@wizery.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  12. Input: synaptics - adjust threshold for treating position values as n…

    Seth Forshee authored and gregkh committed Sep 28, 2012
    …egative
    
    commit 824efd3 upstream.
    
    Commit c039450 (Input: synaptics - handle out of bounds values from the
    hardware) caused any hardware reported values over 7167 to be treated as
    a wrapped-around negative value. It turns out that some firmware uses
    the value 8176 to indicate a finger near the edge of the touchpad whose
    actual position cannot be determined. This value now gets treated as
    negative, which can cause pointer jumps and broken edge scrolling on
    these machines.
    
    I only know of one touchpad which reports negative values, and this
    hardware never reports any value lower than -8 (i.e. 8184). Moving the
    threshold for treating a value as negative up to 8176 should work fine
    then for any hardware we currently know about, and since we're dealing
    with unspecified behavior it's probably the best we can do. The special
    8176 value is also likely to result in sudden jumps in position, so
    let's also clamp this to the maximum specified value for the axis.
    
    BugLink: http://bugs.launchpad.net/bugs/1046512
    https://bugzilla.kernel.org/show_bug.cgi?id=46371
    
    Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
    Reviewed-by: Daniel Kurtz <djkurtz@chromium.org>
    Tested-by: Alan Swanson <swanson@ukfsn.org>
    Tested-by: Arteom <arutemus@gmail.com>
    Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  13. can: mscan-mpc5xxx: fix return value check in mpc512x_can_get_clock()

    Wei Yongjun authored and gregkh committed Sep 21, 2012
    commit f61bd05 upstream.
    
    In case of error, the function clk_get() returns ERR_PTR()
    and never returns NULL pointer. The NULL test in the error
    handling should be replaced with IS_ERR().
    
    dpatch engine is used to auto generated this patch.
    (https://github.com/weiyj/dpatch)
    
    Signed-off-by: Wei Yongjun <yongjun_wei@trendmicro.com.cn>
    Acked-by: Wolfgang Grandegger <wg@grandegger.com>
    Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  14. SCSI: hpsa: Use LUN reset instead of target reset

    smcameron authored and gregkh committed Jul 26, 2012
    commit 21e89af upstream.
    
    It turns out Smart Array logical drives do not support target
    reset and when the target reset fails, the logical drive will
    be taken off line.  Symptoms look like this:
    
    hpsa 0000:03:00.0: Abort request on C1:B0:T0:L0
    hpsa 0000:03:00.0: resetting device 1:0:0:0
    hpsa 0000:03:00.0: cp ffff880037c56000 is reported invalid (probably means target device no longer present)
    hpsa 0000:03:00.0: resetting device failed.
    sd 1:0:0:0: Device offlined - not ready after error recovery
    sd 1:0:0:0: rejecting I/O to offline device
    EXT3-fs error (device sdb1): read_block_bitmap:
    
    LUN reset is supported though, and is what we should be using.
    Target reset is also disruptive in shared SAS situations,
    for example, an external MSA1210m which does support target
    reset attached to Smart Arrays in multiple hosts -- a target
    reset from one host is disruptive to other hosts as all LUNs
    on the target will be reset and will abort all outstanding i/os
    back to all the attached hosts.  So we should use LUN reset,
    not target reset.
    
    Tested this with Smart Array logical drives and with tape drives.
    Not sure how this bug survived since 2009, except it must be very
    rare for a Smart Array to require more than 30s to complete a request.
    
    Signed-off-by: Stephen M. Cameron <scameron@beardog.cce.hp.com>
    Signed-off-by: James Bottomley <JBottomley@Parallels.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  15. SCSI: ibmvscsi: Fix host config length field overflow

    ozbenh authored and gregkh committed Jul 30, 2012
    commit 225c569 upstream.
    
    The length field in the host config packet is only 16-bit long, so
    passing it 0x10000 (64K which is our standard PAGE_SIZE) doesn't
    work and result in an empty config from the server.
    
    Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
    Acked-by: Robert Jennings <rcj@linux.vnet.ibm.com>
    Signed-off-by: James Bottomley <JBottomley@Parallels.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  16. Yama: handle 32-bit userspace prctl

    kees authored and gregkh committed Aug 27, 2012
    commit 2e4930e upstream.
    
    When running a 64-bit kernel and receiving prctls from a 32-bit
    userspace, the "-1" used as an unsigned long will end up being
    misdetected. The kernel is looking for 0xffffffffffffffff instead of
    0xffffffff. Since prctl lacks a distinct compat interface, Yama needs
    to handle this translation itself. As such, support either value as
    meaning PR_SET_PTRACER_ANY, to avoid breaking the ABI for 64-bit.
    
    Signed-off-by: Kees Cook <keescook@chromium.org>
    Acked-by: John Johansen <john.johansen@canonical.com>
    Signed-off-by: James Morris <james.l.morris@oracle.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  17. UBI: erase free PEB with bitflip in EC header

    Matthieu CASTET authored and gregkh committed Aug 22, 2012
    commit 193819c upstream.
    
    Without this patch, these PEB are not scrubbed until we put data in them.
    Bitflip can accumulate latter and we can loose the EC header (but VID header
    should be intact and allow to recover data).
    
    Signed-off-by: Matthieu Castet <matthieu.castet@parrot.com>
    Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  18. UBI: fix autoresize handling in R/O mode

    dedekind authored and gregkh committed Aug 18, 2012
    commit abb3e01 upstream.
    
    Currently UBI fails in autoresize when it is in R/O mode (e.g., because the
    underlying MTD device is R/O). This patch fixes the issue - we just skip
    autoresize and print a warning.
    
    Reported-by: Pali Rohár <pali.rohar@gmail.com>
    Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  19. n_gsm: memory leak in uplink error path

    Russ Gorby authored and gregkh committed Aug 13, 2012
    commit 88ed2a6 upstream.
    
    Uplink (TX) network data will go through gsm_dlci_data_output_framed
    there is a bug where if memory allocation fails, the skb which
    has already been pulled off the list will be lost.
    
    In addition TX skbs were being processed in LIFO order
    
    Fixed the memory leak, and changed to FIFO order processing
    
    Signed-off-by: Russ Gorby <russ.gorby@intel.com>
    Tested-by: Kappel, LaurentX <laurentx.kappel@intel.com>
    Signed-off-by: Alan Cox <alan@linux.intel.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>