1. 11 Sep, 2014 6 commits
  2. 10 Sep, 2014 2 commits
    • Joe Lawrence's avatar
      usb: hub: take hub->hdev reference when processing from eventlist · c605f3cd
      Joe Lawrence authored
      During surprise device hotplug removal tests, it was observed that
      hub_events may try to call usb_lock_device on a device that has already
      been freed. Protect the usb_device by taking out a reference (under the
      hub_event_lock) when hub_events pulls it off the list, returning the
      reference after hub_events is finished using it.
      Signed-off-by: default avatarJoe Lawrence <joe.lawrence@stratus.com>
      Suggested-by: David Bulkow <david.bulkow@stratus.com> for using kref
      Suggested-by: Alan Stern <stern@rowland.harvard.edu> for placement
      Acked-by: default avatarAlan Stern <stern@rowland.harvard.edu>
      Cc: stable <stable@vger.kernel.org>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      c605f3cd
    • Hans de Goede's avatar
      uas: Disable uas on ASM1051 devices · a9c54caa
      Hans de Goede authored
      There are a large numbers of issues with ASM1051 devices in uas mode:
      
      1) They do not support REPORT SUPPORTED OPERATION CODES
      
      2) They use out of spec 8 byte status iu-s when they have no sense data,
         switching to normal 16 byte status iu-s when they do have sense data.
      
      3) They hang / crash when combined with some disks, e.g. a Crucial M500 ssd.
      
      4) They hang / crash when stressed (through e.g. sg_reset --bus) with disks
         with which then normally do work (once 1 & 2 are worked around).
      
      Where as in BOT mode they appear to work fine, so the best way forward with
      these devices is to just blacklist them for uas usage.
      
      Unfortunately this is easier said then done. as older versions of the ASM1053
      (which works fine) use the same usb-id as the ASM1051.
      
      When connected over USB-3 the 2 can be told apart by the number of streams
      they support. So this patch adds some less then pretty code to disable uas for
      the ASM1051. When connected over USB-2, simply disable uas alltogether for
      devices with the shared usb-id.
      
      Cc: stable@vger.kernel.org # 3.16
      Signed-off-by: default avatarHans de Goede <hdegoede@redhat.com>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      a9c54caa
  3. 09 Sep, 2014 6 commits
  4. 08 Sep, 2014 4 commits
  5. 04 Sep, 2014 2 commits
  6. 03 Sep, 2014 14 commits
  7. 01 Sep, 2014 6 commits
    • Bjørn Mork's avatar
      USB: sierra: add 1199:68AA device ID · 5b3da692
      Bjørn Mork authored
      This VID:PID is used for some Direct IP devices behaving
      identical to the already supported 0F3D:68AA devices.
      
      Cc: <stable@vger.kernel.org>
      Reported-by: default avatarLars Melin <larsm17@gmail.com>
      Signed-off-by: default avatarBjørn Mork <bjorn@mork.no>
      Signed-off-by: default avatarJohan Hovold <johan@kernel.org>
      5b3da692
    • Bjørn Mork's avatar
      USB: sierra: avoid CDC class functions on "68A3" devices · 049255f5
      Bjørn Mork authored
      Sierra Wireless Direct IP devices using the 68A3 product ID
      can be configured for modes including a CDC ECM class function.
      The known example uses interface numbers 12 and 13 for the ECM
      control and data interfaces respectively, consistent with CDC
      MBIM function interface numbering on other Sierra devices.
      
      It seems cleaner to restrict this driver to the ff/ff/ff
      vendor specific interfaces rather than increasing the already
      long interface number blacklist.  This should be more future
      proof if Sierra adds more class functions using interface
      numbers not yet in the blacklist.
      
      Cc: <stable@vger.kernel.org>
      Signed-off-by: default avatarBjørn Mork <bjorn@mork.no>
      Signed-off-by: default avatarJohan Hovold <johan@kernel.org>
      049255f5
    • Johan Hovold's avatar
      USB: ftdi_sio: add support for NOVITUS Bono E thermal printer · ee444609
      Johan Hovold authored
      Add device id for NOVITUS Bono E thermal printer.
      Reported-by: default avatarEmanuel Koczwara <poczta@emanuelkoczwara.pl>
      Cc: stable <stable@vger.kernel.org>
      Signed-off-by: default avatarJohan Hovold <johan@kernel.org>
      ee444609
    • Johan Hovold's avatar
      USB: zte_ev: fix removed PIDs · 4df0ea41
      Johan Hovold authored
      Add back some PIDs that were mistakingly remove when reverting commit
      73228a05 ("USB: option,zte_ev: move most ZTE CDMA devices to
      zte_ev"), which apparently did more than its commit message claimed in
      that it not only moved some PIDs from option to zte_ev but also added
      some new ones.
      
      Fixes: 63a901c0 ("Revert "USB: option,zte_ev: move most ZTE CDMA
      devices to zte_ev"")
      Reported-by: default avatarLei Liu <lei35151@163.com>
      Cc: stable <stable@vger.kernel.org>
      4df0ea41
    • Linus Torvalds's avatar
      Linux 3.17-rc3 · 69e273c0
      Linus Torvalds authored
      69e273c0
    • Linus Torvalds's avatar
      Merge tag 'xtensa-20140830' of git://github.com/czankel/xtensa-linux · 05bdb8c9
      Linus Torvalds authored
      Pull Xtensa updates from Chris Zankel:
       "Xtensa improvements for 3.17:
         - support highmem on cores with aliasing data cache.  Enable highmem
           on kc705 by default
         - simplify addition of new core variants (no need to modify Kconfig /
           Makefiles)
         - improve robustness of unaligned access handler and its interaction
           with window overflow/underflow exception handlers
         - deprecate atomic and spill registers syscalls
         - clean up Kconfig: remove orphan MATH_EMULATION, sort 'select'
           statements
         - wire up renameat2 syscall.
      
        Various fixes:
         - fix address checks in dma_{alloc,free}_coherent (runtime BUG)
         - fix access to THREAD_RA/THREAD_SP/THREAD_DS (debug build breakage)
         - fix TLBTEMP_BASE_2 region handling in fast_second_level_miss
           (runtime unrecoverable exception)
         - fix a6 and a7 handling in fast_syscall_xtensa (runtime userspace
           register clobbering)
         - fix kernel/user jump out of fast_unaligned (potential runtime
           unrecoverabl exception)
         - replace termios IOCTL code definitions with constants (userspace
           build breakage)"
      
      * tag 'xtensa-20140830' of git://github.com/czankel/xtensa-linux: (25 commits)
        xtensa: deprecate fast_xtensa and fast_spill_registers syscalls
        xtensa: don't allow overflow/underflow on unaligned stack
        xtensa: fix a6 and a7 handling in fast_syscall_xtensa
        xtensa: allow single-stepping through unaligned load/store
        xtensa: move invalid unaligned instruction handler closer to its users
        xtensa: make fast_unaligned store restartable
        xtensa: add double exception fixup handler for fast_unaligned
        xtensa: fix kernel/user jump out of fast_unaligned
        xtensa: configure kc705 for highmem
        xtensa: support highmem in aliasing cache flushing code
        xtensa: support aliasing cache in kmap
        xtensa: support aliasing cache in k[un]map_atomic
        xtensa: implement clear_user_highpage and copy_user_highpage
        xtensa: fix TLBTEMP_BASE_2 region handling in fast_second_level_miss
        xtensa: allow fixmap and kmap span more than one page table
        xtensa: make fixmap region addressing grow with index
        xtensa: fix access to THREAD_RA/THREAD_SP/THREAD_DS
        xtensa: add renameat2 syscall
        xtensa: fix address checks in dma_{alloc,free}_coherent
        xtensa: replace IOCTL code definitions with constants
        ...
      05bdb8c9