linux-kernel - Re: [PATCH] UFS: Make TM command timeout configurable from host side

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: <7acf375efe2047f9def4de208980fbd2e0e29b34.camel@mediatek.com>
Date: Tue, 18 Nov 2025 05:52:38 +0000
From: Peter Wang (王信友) <peter.wang@...iatek.com>
To: "linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
	"bvanassche@....org" <bvanassche@....org>, "hare@...e.de" <hare@...e.de>,
	"martin.petersen@...cle.com" <martin.petersen@...cle.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] UFS: Make TM command timeout configurable from host side

On Mon, 2025-11-17 at 08:40 -0800, Bart Van Assche wrote
> 
> Hannes, do you agree with increasing the max_active argument from 1
> to
> INT_MAX? I think the above code was introduced 12 years ago by commit
> e494f6a72839 ("[SCSI] improved eh timeout handler").
> 
> Thanks,
> 
> Bart.

Hi Bart,

I think we can change max_active, but using the default value of 0 
should be sufficient, according to workqueue.rst.

The maximum limit for ``@..._active`` is 2048 and the default value
used
when 0 is specified is 1024. These values are chosen sufficiently high
such that they are not the limiting factor while providing protection
in
runaway cases.

Thanks
Peter