Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Commits on Sep 9, 2009
  1. @gregkh

    Linux 2.6.30.6

    gregkh authored
  2. @gregkh

    ocfs2: ocfs2_write_begin_nolock() should handle len=0

    Sunil Mushran authored gregkh committed
    commit 8379e7c upstream.
    
    Bug introduced by mainline commit e743267
    The bug causes ocfs2_write_begin_nolock() to oops when len=0.
    
    Signed-off-by: Sunil Mushran <sunil.mushran@oracle.com>
    Signed-off-by: Joel Becker <joel.becker@oracle.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  3. @jirislaby @gregkh

    NET: llc, zero sockaddr_llc struct

    jirislaby authored gregkh committed
    commit 28e9fc5 upstream.
    
    sllc_arphrd member of sockaddr_llc might not be changed. Zero sllc
    before copying to the above layer's structure.
    
    Signed-off-by: Jiri Slaby <jirislaby@gmail.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  4. @gregkh

    rose: Fix rose_getname() leak

    Eric Dumazet authored gregkh committed
    commit 17ac2e9 upstream.
    
    rose_getname() can leak kernel memory to user.
    
    Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  5. @gregkh

    econet: Fix econet_getname() leak

    Eric Dumazet authored gregkh committed
    commit 80922bb upstream.
    
    econet_getname() can leak kernel memory to user.
    
    Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  6. @gregkh

    netrom: Fix nr_getname() leak

    Eric Dumazet authored gregkh committed
    commit f6b97b2 upstream.
    
    nr_getname() can leak kernel memory to user.
    
    Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  7. @gregkh

    appletalk: fix atalk_getname() leak

    Eric Dumazet authored gregkh committed
    commit 3d39247 upstream.
    
    atalk_getname() can leak 8 bytes of kernel memory to user
    
    Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  8. @gregkh

    irda: Fix irda_getname() leak

    Eric Dumazet authored gregkh committed
    commit 09384df upstream.
    
    irda_getname() can leak kernel memory to user.
    
    Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  9. @gregkh

    can: Fix raw_getname() leak

    Eric Dumazet authored gregkh committed
    commit e84b90a upstream.
    
    raw_getname() can leak 10 bytes of kernel memory to user
    
    (two bytes hole between can_family and can_ifindex,
    8 bytes at the end of sockaddr_can structure)
    
    Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>
    Acked-by: Oliver Hartkopp <oliver@hartkopp.net>
    Signed-off-by: David S. Miller <davem@davemloft.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  10. @michich @gregkh

    xenfb: connect to backend before registering fb

    michich authored gregkh committed
    commit 0a80fb1 upstream.
    
    As soon as the framebuffer is registered, our methods may be called by the
    kernel. This leads to a crash as xenfb_refresh() gets called before we have
    the irq.
    
    Connect to the backend before registering our framebuffer with the kernel.
    
    [ Fixes bug http://bugzilla.kernel.org/show_bug.cgi?id=14059 ]
    
    Signed-off-by: Michal Schmidt <mschmidt@redhat.com>
    Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  11. @error27 @gregkh

    ar9170: fix read & write outside array bounds

    error27 authored gregkh committed
    commit e9d126c upstream.
    
    Backport done by Christian Lamparter <chunkeey@googlemail.com>
    
    queue == __AR9170_NUM_TXQ would cause a bug on the next line.
    
    found by Smatch ( http://repo.or.cz/w/smatch.git ).
    
    Reported-by: Dan Carpenter <error27@gmail.com>
    Signed-off-by: Dan Carpenter <error27@gmail.com>
    Signed-off-by: Christian Lamparter <chunkeey@web.de>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  12. @gregkh

    ipv4: make ip_append_data() handle NULL routing table

    Julien TINNES authored gregkh committed
    commit 788d908 upstream.
    
    Add a check in ip_append_data() for NULL *rtp to prevent future bugs in
    callers from being exploitable.
    
    Signed-off-by: Julien Tinnes <julien@cr0.org>
    Signed-off-by: Tavis Ormandy <taviso@sdf.lonestar.org>
    Acked-by: David S. Miller <davem@davemloft.net>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  13. @gregkh

    powerpc/ps3: Add missing check for PS3 to rtc-ps3 platform device reg…

    Geert Uytterhoeven authored gregkh committed
    …istration
    
    commit 7b6a09f upstream.
    
    On non-PS3, we get:
    
    | kernel BUG at drivers/rtc/rtc-ps3.c:36!
    
    because the rtc-ps3 platform device is registered unconditionally in a kernel
    with builtin support for PS3.
    
    Reported-by: Sachin Sant <sachinp@in.ibm.com>
    Signed-off-by: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
    Acked-by: Geoff Levand <geoffrey.levand@am.sony.com>
    Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  14. @gregkh

    USB: EHCI: fix two new bugs related to Clear-TT-Buffer

    Alan Stern authored gregkh committed
    commit 7a0f0d9 upstream.
    
    This patch (as1273) fixes two(!) bugs introduced by the new
    Clear-TT-Buffer implementation in ehci-hcd.
    
    	It is now possible for an idle QH to have some URBs on its
    	queue -- this will happen if a Clear-TT-Buffer is pending for
    	the QH's endpoint.  Consequently we should not issue a warning
    	when someone tries to unlink an URB from an idle QH; instead
    	we should process the request immediately.
    
    	The refcounts for QHs could get messed up, because
    	submit_async() would increment the refcount when calling
    	qh_link_async() and qh_link_async() would then refuse to link
    	the QH into the schedule if a Clear-TT-Buffer was pending.
    	Instead we should increment the refcount only when the QH
    	actually is added to the schedule.  The current code tries to
    	be clever by leaving the refcount alone if an unlink is
    	immediately followed by a relink; the patch changes this to an
    	unconditional decrement and increment (although they occur in
    	the opposite order).
    
    Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
    CC: David Brownell <david-b@pacbell.net>
    Tested-by: Manuel Lauss <manuel.lauss@gmail.com>
    Tested-by: Matthijs Kooijman <matthijs@stdin.nl>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  15. @gregkh

    USB: EHCI: use the new clear_tt_buffer interface

    Alan Stern authored gregkh committed
    commit 914b701 upstream.
    
    This patch (as1256) changes ehci-hcd and all the other drivers in the
    EHCI family to make use of the new clear_tt_buffer callbacks.  When a
    Clear-TT-Buffer request is in progress for a QH, the QH is not allowed
    to be linked into the async schedule until the request is finished.
    At that time, if there are any URBs queued for the QH, it is linked
    into the async schedule.
    
    Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  16. @gregkh

    USB: fix the clear_tt_buffer interface

    Alan Stern authored gregkh committed
    commit cb88a1b upstream.
    
    This patch (as1255) updates the interface for calling
    usb_hub_clear_tt_buffer().  Even the name of the function is changed!
    
    When an async URB (i.e., Control or Bulk) going through a high-speed
    hub to a non-high-speed device is cancelled or fails, the hub's
    Transaction Translator buffer may be left busy still trying to
    complete the transaction.  The buffer has to be cleared; that's what
    usb_hub_clear_tt_buffer() does.
    
    It isn't safe to send any more URBs to the same endpoint until the TT
    buffer is fully clear.  Therefore the HCD needs to be told when the
    Clear-TT-Buffer request has finished.  This patch adds a callback
    method to struct hc_driver for that purpose, and makes the hub driver
    invoke the callback at the proper time.
    
    The patch also changes a couple of names; "hub_tt_kevent" and
    "tt.kevent" now look rather antiquated.
    
    Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  17. @gregkh

    ipv6: Fix commit 63d9950 (ipv6: Make v4-mapped bindings consistent wi…

    Bruno Prémont authored gregkh committed
    …th IPv4)
    
    commit ca6982b upstream.
    
    Commit 63d9950
      (ipv6: Make v4-mapped bindings consistent with IPv4)
    changes behavior of inet6_bind() for v4-mapped addresses so it should
    behave the same way as inet_bind().
    
    During this change setting of err to -EADDRNOTAVAIL got lost:
    
    af_inet.c:469 inet_bind()
    	err = -EADDRNOTAVAIL;
    	if (!sysctl_ip_nonlocal_bind &&
    	    !(inet->freebind || inet->transparent) &&
    	    addr->sin_addr.s_addr != htonl(INADDR_ANY) &&
    	    chk_addr_ret != RTN_LOCAL &&
    	    chk_addr_ret != RTN_MULTICAST &&
    	    chk_addr_ret != RTN_BROADCAST)
    		goto out;
    
    
    af_inet6.c:463 inet6_bind()
    	if (addr_type == IPV6_ADDR_MAPPED) {
    		int chk_addr_ret;
    
    		/* Binding to v4-mapped address on a v6-only socket
    		 * makes no sense
    		 */
    		if (np->ipv6only) {
    			err = -EINVAL;
    			goto out;
    		}
    
    		/* Reproduce AF_INET checks to make the bindings consitant */
    		v4addr = addr->sin6_addr.s6_addr32[3];
    		chk_addr_ret = inet_addr_type(net, v4addr);
    		if (!sysctl_ip_nonlocal_bind &&
    		    !(inet->freebind || inet->transparent) &&
    		    v4addr != htonl(INADDR_ANY) &&
    		    chk_addr_ret != RTN_LOCAL &&
    		    chk_addr_ret != RTN_MULTICAST &&
    		    chk_addr_ret != RTN_BROADCAST)
    			goto out;
    	} else {
    
    
    Signed-off-by: Bruno Prémont <bonbons@linux-vserver.org>
    Signed-off-by: David S. Miller <davem@davemloft.net>
  18. @utrace @gregkh

    kthreads: fix kthread_create() vs kthread_stop() race

    utrace authored gregkh committed
    The bug should be "accidently" fixed by recent changes in 2.6.31,
    all kernels <= 2.6.30 need the fix. The problem was never noticed before,
    it was found because it causes mysterious failures with GFS mount/umount.
    
    Credits to Robert Peterson. He blaimed kthread.c from the very beginning.
    But, despite my promise, I forgot to inspect the old implementation until
    he did a lot of testing and reminded me. This led to huge delay in fixing
    this bug.
    
    kthread_stop() does put_task_struct(k) before it clears kthread_stop_info.k.
    This means another kthread_create() can re-use this task_struct, but the
    new kthread can still see kthread_should_stop() == T and exit even without
    calling threadfn().
    
    Reported-by: Robert Peterson <rpeterso@redhat.com>
    Tested-by: Robert Peterson <rpeterso@redhat.com>
    Signed-off-by: Oleg Nesterov <oleg@redhat.com>
    Acked-by: Rusty Russell <rusty@rustcorp.com.au>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  19. @gregkh

    gspca - ov534: Fix ov772x

    Jean-Francois Moine authored gregkh committed
    The scan of the image packets of the sensor ov772x was broken when
    the sensor ov965x was added.
    
    [ Based on upstream c874f3a, modified slightly for v2.6.30.5 ]
    
    Signed-off-by: Jim Paris <jim@jtan.com>
    Acked-by: Jean-Francois Moine <moinejf@free.fr>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  20. @gregkh

    xfs: fix spin_is_locked assert on uni-processor builds

    Christoph Hellwig authored gregkh committed
    upstream commit a8914f3
    
    Without SMP or preemption spin_is_locked always returns false,
    so we can't do an assert with it.  Instead use assert_spin_locked,
    which does the right thing on all builds.
    
    
    Signed-off-by: Christoph Hellwig <hch@lst.de>
    Reviewed-by: Eric Sandeen <sandeen@sandeen.net>
    Reported-by: Johannes Engel <jcnengel@googlemail.com>
    Tested-by: Johannes Engel <jcnengel@googlemail.com>
    Signed-off-by: Felix Blyakher <felixb@sgi.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  21. @gregkh

    xfs: fix freeing of inodes not yet added to the inode cache

    Christoph Hellwig authored gregkh committed
    upstream commit b36ec04
    
    When freeing an inode that lost race getting added to the inode cache we
    must not call into ->destroy_inode, because that would delete the inode
    that won the race from the inode cache radix tree.
    
    This patch uses splits a new xfs_inode_free helper out of xfs_ireclaim
    and uses that plus __destroy_inode to make sure we really only free
    the memory allocted for the inode that lost the race, and not mess with
    the inode cache state.
    
    Signed-off-by: Christoph Hellwig <hch@lst.de>
    Reviewed-by: Eric Sandeen <sandeen@sandeen.net>
    Reported-by: Alex Samad <alex@samad.com.au>
    Reported-by: Andrew Randrianasulu <randrik@mail.ru>
    Reported-by: Stephane <sharnois@max-t.com>
    Reported-by: Tommy <tommy@news-service.com>
    Reported-by: Miah Gregory <mace@darksilence.net>
    Reported-by: Gabriel Barazer <gabriel@oxeva.fr>
    Reported-by: Leandro Lucarella <llucax@gmail.com>
    Reported-by: Daniel Burr <dburr@fami.com.au>
    Reported-by: Nickolay <newmail@spaces.ru>
    Reported-by: Michael Guntsche <mike@it-loops.com>
    Reported-by: Dan Carley <dan.carley+linuxkern-bugs@gmail.com>
    Reported-by: Michael Ole Olsen <gnu@gmx.net>
    Reported-by: Michael Weissenbacher <mw@dermichi.com>
    Reported-by: Martin Spott <Martin.Spott@mgras.net>
    Reported-by: Christian Kujau <lists@nerdbynature.de>
    Tested-by: Michael Guntsche <mike@it-loops.com>
    Tested-by: Dan Carley <dan.carley+linuxkern-bugs@gmail.com>
    Tested-by: Christian Kujau <lists@nerdbynature.de>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  22. @gregkh

    vfs: add __destroy_inode

    Christoph Hellwig authored gregkh committed
    backport of upstream commit 2e00c97
    
    When we want to tear down an inode that lost the add to the cache race
    in XFS we must not call into ->destroy_inode because that would delete
    the inode that won the race from the inode cache radix tree.
    
    This patch provides the __destroy_inode helper needed to fix this,
    the actual fix will be in th next patch.  As XFS was the only reason
    destroy_inode was exported we shift the export to the new __destroy_inode.
    
    Signed-off-by: Christoph Hellwig <hch@lst.de>
    Reviewed-by: Eric Sandeen <sandeen@sandeen.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  23. @gregkh

    vfs: fix inode_init_always calling convention

    Christoph Hellwig authored gregkh committed
    backport of upstream commit 54e3462
    
    Currently inode_init_always calls into ->destroy_inode if the additional
    initialization fails.  That's not only counter-intuitive because
    inode_init_always did not allocate the inode structure, but in case of
    XFS it's actively harmful as ->destroy_inode might delete the inode from
    a radix-tree that has never been added.  This in turn might end up
    deleting the inode for the same inum that has been instanciated by
    another process and cause lots of cause subtile problems.
    
    Also in the case of re-initializing a reclaimable inode in XFS it would
    free an inode we still want to keep alive.
    
    Signed-off-by: Christoph Hellwig <hch@lst.de>
    Reviewed-by: Eric Sandeen <sandeen@sandeen.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  24. @gregkh

    ACPI processor: force throttling state when BIOS returns incorrect value

    Frans Pop authored gregkh committed
    commit 2a90800 upstream.
    
    If the BIOS reports an invalid throttling state (which seems to be
    fairly common after system boot), a reset is done to state T0.
    Because of a check in acpi_processor_get_throttling_ptc(), the reset
    never actually gets executed, which results in the error reoccurring
    on every access of for example /proc/acpi/processor/CPU0/throttling.
    
    Add a 'force' option to acpi_processor_set_throttling() to ensure
    the reset really takes effect.
    
    Addresses http://bugzilla.kernel.org/show_bug.cgi?id=13389
    
    This patch, together with the next one, fixes a regression introduced in
    2.6.30, listed on the regression list. They have been available for 2.5
    months now in bugzilla, but have not been picked up, despite various
    reminders and without any reason given.
    
    Google shows that numerous people are hitting this issue. The issue is in
    itself relatively minor, but the bug in the code is clear.
    
    The patches have been in all my kernels and today testing has shown that
    throttling works correctly with the patches applied when the system
    overheats (http://bugzilla.kernel.org/show_bug.cgi?id=13918#c14).
    
    Signed-off-by: Frans Pop <elendil@planet.nl>
    Acked-by: Zhang Rui <rui.zhang@intel.com>
    Cc: Len Brown <lenb@kernel.org>
    Cc: "Rafael J. Wysocki" <rjw@sisk.pl>
    Cc: Rusty Russell <rusty@rustcorp.com.au>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  25. @gregkh

    ocfs2: Initialize the cluster we're writing to in a non-sparse extend

    Sunil Mushran authored gregkh committed
    commit e743267 upstream.
    
    In a non-sparse extend, we correctly allocate (and zero) the clusters between
    the old_i_size and pos, but we don't zero the portions of the cluster we're
    writing to outside of pos<->len.
    
    It handles clustersize > pagesize and blocksize < pagesize.
    
    [Cleaned up by Joel Becker.]
    
    Signed-off-by: Sunil Mushran <sunil.mushran@oracle.com>
    Signed-off-by: Joel Becker <joel.becker@oracle.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  26. @jsgf @gregkh

    x86, amd: Don't probe for extended APIC ID if APICs are disabled

    jsgf authored gregkh committed
    commit 2cb0786 upstream.
    
    If we've logically disabled apics, don't probe the PCI space for the
    AMD extended APIC ID.
    
    [ Impact: prevent boot crash under Xen. ]
    
    Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
    Reported-by: Bastian Blank <bastian@waldi.eu.org>
    Signed-off-by: H. Peter Anvin <hpa@zytor.com>
    Cc: Andreas Herrmann <andreas.herrmann3@amd.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  27. @gregkh

    Bug Fix arch/ia64/kernel/pci-dma.c: fix recursive dma_supported() cal…

    Fenghua Yu authored gregkh committed
    …l in iommu_dma_supported()
    
    commit 51b89f7 upstream.
    
    In commit 160c1d8,
    dma_ops->dma_supported = iommu_dma_supported;
    
    This dma_ops->dma_supported is first called in platform_dma_init() during kernel
    boot. Then dma_ops->dma_supported will be called recursively in
    iommu_dma_supported.
    
    Kernel can not boot because kernel can not get out of iommu_dma_supported until
    it runs out of stack memory.
    
    Signed-off-by: Fenghua Yu <fenghua.yu@intel.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  28. @torvalds @gregkh

    do_sigaltstack: avoid copying 'stack_t' as a structure to user space

    torvalds authored gregkh committed
    commit 0083fc2 upstream.
    
    Ulrich Drepper correctly points out that there is generally padding in
    the structure on 64-bit hosts, and that copying the structure from
    kernel to user space can leak information from the kernel stack in those
    padding bytes.
    
    Avoid the whole issue by just copying the three members one by one
    instead, which also means that the function also can avoid the need for
    a stack frame.  This also happens to match how we copy the new structure
    from user space, so it all even makes sense.
    
    [ The obvious solution of adding a memset() generates horrid code, gcc
      does really stupid things. ]
    
    Reported-by: Ulrich Drepper <drepper@redhat.com>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  29. @gregkh

    mpt2sas: fix config request and diag reset deadlock

    Kashyap, Desai authored gregkh committed
    commit 388ce4b upstream.
    
    Moving the setting and clearing of the mutex's to
    _config_request. There was a mutex deadlock when diag reset is called from
    inside _config_request, so diag reset was moved to outside the mutexs.
    
    Signed-off-by: James Bottomley <James.Bottomley@suse.de>
    Signed-off-by: Kashyap Desai <kashyap.desai@lsi.com>
    Signed-off-by: Eric Moore <Eric.moore@lsi.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  30. @gregkh

    SCSI: mpt2sas: fix oops because drv data points to NULL on resume fro…

    Kashyap, Desai authored gregkh committed
    …m hibernate
    
    commit fcfe639 upstream.
    
    Fix another ocurring when the system resumes.  This oops was due to driver
    setting the pci drvdata to NULL on the prior hibernation.  Becuase it was
    set to NULL, upon resmume we assume the pci drvdata is non-zero, and we oops.
    To fix the ooops, we don't set pci drvdata to NULL at hibernation time.
    
    Signed-off-by: Kashyap Desai <kashyap.desai@lsi.com>
    Signed-off-by: James Bottomley <James.Bottomley@suse.de>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  31. @gregkh

    SCSI: mpt2sas: fix crash due to Watchdog is active while OS in standb…

    Kashyap, Desai authored gregkh committed
    …y mode
    
    commit e4750c9 upstream.
    
    Fix oops ocurring at hibernation time.  This oops was due to the firmware fault
    watchdog timer still running after we freed resources. To fix the issue we need
    to terminate the watchdog timer at hibernation time.
    
    Signed-off-by: Kashyap Desai <kashyap.desai@lsi.com>
    Signed-off-by: James Bottomley <James.Bottomley@suse.de>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  32. @gregkh

    SCSI: mpt2sas: fix infinite loop inside config request

    Kashyap, Desai authored gregkh committed
    commit 6bd4e1e upstream.
    
    This restriction is introduced just to avoid loop of
    config_request. Retry must be limited so we have restricted
    config request to maximum 2 times.
    
    Signed-off-by: Kashyap Desai <kashyap.desai@lsi.com>
    Signed-off-by: James Bottomley <James.Bottomley@suse.de>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  33. @gregkh

    SCSI: mpt2sas: Excessive log info causes sas iounit page time out

    Kashyap, Desai authored gregkh committed
    commit be9e8cd upstream.
    
    Inhibit 0x3117 loginfos - during cable pull, there are too many printks going
    to the syslog, this is have impact on how fast the interrupt routine can handle
    keeping up with command completions; this was the root cause to the config
    pages timeouts.
    
    Signed-off-by: Kashyap Desai <kashyap.desai@lsi.com>
    Signed-off-by: James Bottomley <James.Bottomley@suse.de>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  34. @gregkh

    SCSI: mpt2sas: Raid 10 Value is showing as Raid 1E in /va/log/messages

    Kashyap, Desai authored gregkh committed
    commit 62727a7 upstream.
    
    When a volume is activated, the driver will recieve a pair of ir config change
    events to remove the foreign volume, then add the native.
    In the process of the removal event, the hidden raid componet is removed from
    the parent.When the disks is added back, the adding of the port fails becuase
    there is no instance of the device in its parent.
    To fix this issue, the driver needs to call mpt2sas_transport_update_links()
    prior to calling _scsih_add_device. In addition, we added sanity checks on
    volume add and removal to ignore events for foreign volumes.
    
    Signed-off-by: Kashyap Desai <kashyap.desai@lsi.com>
    Signed-off-by: James Bottomley <James.Bottomley@suse.de>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  35. @gregkh

    SCSI: mpt2sas: Expander fix oops saying "Already part of another port"

    Kashyap, Desai authored gregkh committed
    commit 20f5895 upstream.
    
    Kernel panic is seen because driver did not tear down the port which should
    be dnoe using mpt2sas_transport_port_remove(). without this fix When expander
    is added back we would oops inside sas_port_add_phy.
    
    Signed-off-by: Kashyap Desai <kashyap.desai@lsi.com>
    Signed-off-by: James Bottomley <James.Bottomley@suse.de>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Something went wrong with that request. Please try again.