linux-kernel - Re: [PATCH v2] usb: storage: Ignore UAS driver for SanDisk Extreme Pro 55AF storage device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4bac2d53-0e5b-437e-92bc-12921a8efd8d@kylinos.cn>
Date: Tue, 8 Jul 2025 13:55:47 +0800
From: Jie Deng <dengjie03@...inos.cn>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: stern@...land.harvard.edu, linux-kernel@...r.kernel.org,
 linux-usb@...r.kernel.org, usb-storage@...ts.one-eyed-alien.net
Subject: Re: [PATCH v2] usb: storage: Ignore UAS driver for SanDisk Extreme
 Pro 55AF storage device


在 2025/7/7 16:49, Greg KH 写道:
> On Mon, Jul 07, 2025 at 02:25:07PM +0800, Jie Deng wrote:
>> The SanDisk Extreme Pro 55AF storage device(0781:55af) has poor compatibility with UAS drivers.
>> The logs:
>> [    1.359859][ 0] [  T163] usb 2-1: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd
> Nit, the [] stuff should all be removed, it's not relevant, right?
>
>> [    1.385708][ 0] [  T163] usb 2-1: New USB device found, idVendor=0781, idProduct=55af, bcdDevice=10.85
>> [    1.385709][ 0] [  T163] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
>> [    1.385710][ 0] [  T163] usb 2-1: Product: Extreme Pro 55AF
>> [    1.385711][ 0] [  T163] usb 2-1: Manufacturer: SanDisk
>> [    1.385711][ 0] [  T163] usb 2-1: SerialNumber: 323234323935343030343636
>> [    1.927603][ 0] [  T306] usbcore: registered new interface driver usb-storage
>> [    1.940511][ 0] [  T306] scsi host3: uas
>> [    1.940584][ 0] [  T306] usbcore: registered new interface driver uas
>> [    1.940843][ 0] [  T188] scsi 3:0:0:0: Direct-Access     SanDisk  Extreme Pro 55AF 1085 PQ: 0 ANSI: 6
>> [    1.941363][ 0] [  T188] scsi 3:0:0:1: Enclosure         SanDisk  SES Device       1085 PQ: 0 ANSI: 6
>> [    1.941697][ 0] [  T188] sd 3:0:0:0: Attached scsi generic sg0 type 0
>> [    1.941783][ 0] [  T188] scsi 3:0:0:1: Attached scsi generic sg1 type 13
>> [    1.942296][ 0] [  T189] sd 3:0:0:0: [sda] 1953459617 512-byte logical blocks: (1.00 TB/931 GiB)
>> [    1.942373][ 0] [  T189] sd 3:0:0:0: [sda] Write Protect is off
>> [    1.942374][ 0] [  T189] sd 3:0:0:0: [sda] Mode Sense: 37 00 10 00
>> [    1.942534][ 0] [  T189] sd 3:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
>> [    1.943586][ 0] [  T189] sd 3:0:0:0: [sda] Optimal transfer size 2097152 bytes
>> [    1.976797][ 0] [  T189]  sda: sda1
>> [    1.977898][ 0] [  T189] sd 3:0:0:0: [sda] Attached SCSI disk
>> [    1.980406][ 0] [  T267] scsi 3:0:0:1: Failed to get diagnostic page 0x1
>> [    1.980408][ 0] [  T267] scsi 3:0:0:1: Failed to bind enclosure -19
>> [    1.980414][ 0] [  T267] ses 3:0:0:1: Attached Enclosure device
>> [    1.981068][ 0] [    C0] sd 3:0:0:0: [sda] tag#10 data cmplt err -75 uas-tag 1 inflight: CMD
>> [    1.981071][ 0] [    C0] sd 3:0:0:0: [sda] tag#10 CDB: Read(10) 28 00 74 6f 6d 00 00 00 08 00
>> [   33.819186][ 0] [  T188] sd 3:0:0:0: [sda] tag#10 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD
>> [   33.819188][ 0] [  T188] sd 3:0:0:0: [sda] tag#10 CDB: Read(10) 28 00 74 6f 6d 00 00 00 08 00
>> [   33.843186][ 0] [  T309] scsi host3: uas_eh_device_reset_handler start
> So new devices are being made that can not handle UAS?  Are you sure
> there's not some other quirk that could be used here instead?  How does
> this device work on other operating systems with the UAS drivers there?
>
> thanks,
>
> greg k-h
Thank you for your reply.

1. The information within [] is redundant and should be removed
2. Regarding your question, before submitting the patch,
I conducted the following tests:
1) linux + x86: The SanDisk Extreme Pro 55AF device can be recognized
normally when using the uas driver. USB controller model (VendorID:
1D94, DeviceID: 145F,Chengdu Haiguang IC Design Co., Ltd.USB 3.0 Host 
controller)
2) linux + arm64: The SanDisk Extreme Pro 55AF device will report an 
error when
using the uas driver and the driver cannot be loaded. USB Controller model
(Vendor ID: 1912, Device ID: 0014,uPD720201 USB 3.0 Host Controller).
3) linux + arm64: Add the parameter "USB-storage.quirks =0781:55af:u" in 
grub.
The SanDisk Extreme Pro 55AF device runs the usb storage driver without 
any error
and can be recognized normally.