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] [day] [month] [year] [list]

Message-ID: <0056f856-bd81-403d-84cb-339a37a73b8f@kylinos.cn>
Date: Thu, 10 Jul 2025 14:28:43 +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/9 14:21, Greg KH 写道:
> On Wed, Jul 09, 2025 at 11:40:03AM +0800, Jie Deng wrote:
>> 在 2025/7/8 15:33, Greg KH 写道:
>>>> 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).
>>> Ok, that sounds like an arm64 issue we should resolve.  Why can the
>>> driver not be loaded at all?  What happens?
>> 1. During the process of loading the uas driver, the following error message
>> will occur,
>> resulting in the failure of driver loading:
>> scsi 3:0:0:1: Failed to get diagnostic page 0x1
>> scsi 3:0:0:1: Failed to bind enclosure -19
>> ses 3:0:0:1: Attached Enclosure device
>> sd 3:0:0:0: [sda] tag#10 data cmplt err -75 uas-tag 1 inflight: CMD
>> sd 3:0:0:0: [sda] tag#10 CDB: Read(10) 28 00 74 6f 6d 00 00 00 08 00
>> sd 3:0:0:0: [sda] tag#10 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD
>> sd 3:0:0:0: [sda] tag#10 CDB: Read(10) 28 00 74 6f 6d 00 00 00 08 00
> Any chance you can use usbmon to try to figure out why the arm64 system
> is sending different commands or failures than x86 is?
Thank you for your suggestions. I’ll review them thoroughly going 
forward.🙂