linux-kernel - Re: [PATCH] usbip: Fix the error limitation on max_hw

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

Message-ID: <247c7e15-bbff-427f-8315-ca463f8b933b@linuxfoundation.org>
Date: Thu, 27 Feb 2025 15:23:25 -0700
From: Shuah Khan <skhan@...uxfoundation.org>
To: Zongmin Zhou <min_halo@....com>
Cc: valentina.manea.m@...il.com, shuah@...nel.org, i@...ithal.me,
 gregkh@...uxfoundation.org, linux-usb@...r.kernel.org,
 linux-kernel@...r.kernel.org, Zongmin Zhou <zhouzongmin@...inos.cn>,
 Shuah Khan <skhan@...uxfoundation.org>
Subject: Re: [PATCH] usbip: Fix the error limitation on max_hw_sectors for
 usbip device

On 2/24/25 01:36, Zongmin Zhou wrote:
> Dear Shuah,
> 
> 
> Yes，the usbip server get the real USB controller message send to usbip client vhci-hcd，
> 
> must have to changethe API between the kernel and user-space.
> 
> The easiest way is to simply set vhci-hcd dma mask to 64 by default,
> 
> but not all USB controllers support 64bit，That doesn't look good？

This is an expetnsive change to fix the problem. In addition this change
is unnecessary for non-storage devices where USB over IP is used.
You mentioned this happens only in swiotlb cases? Can you explain the
configuration on host and client side.

I would like to explore fixes that are simpler than what is proposed
in this patch.

thanks,
-- Shuah