netdev - Re: [net v2] net: wwan: t7xx: Fix FSM command timeout issue

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: <6d839f1a-9c38-46a9-aa3b-62afbd75cea7@gmail.com>
Date: Sun, 22 Dec 2024 23:04:51 +0200
From: Sergey Ryazanov <ryazanov.s.a@...il.com>
To: Jinjian Song <jinjian.song@...ocom.com>
Cc: chandrashekar.devegowda@...el.com, chiranjeevi.rapolu@...ux.intel.com,
 haijun.liu@...iatek.com, ricardo.martinez@...ux.intel.com,
 loic.poulain@...aro.org, andrew+netdev@...n.ch,
 angelogioacchino.delregno@...labora.com, corbet@....net,
 danielwinkler@...gle.com, helgaas@...nel.org, horms@...nel.org,
 korneld@...gle.com, linux-arm-kernel@...ts.infradead.org,
 linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
 linux-mediatek@...ts.infradead.org, matthias.bgg@...il.com,
 netdev@...r.kernel.org, johannes@...solutions.net, davem@...emloft.net,
 edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com
Subject: Re: [net v2] net: wwan: t7xx: Fix FSM command timeout issue

Hi Jinjian,

On 20.12.2024 10:50, Jinjian Song wrote:
> From: Sergey Ryazanov <ryazanov.s.a@...il.com>
> 
>>> Fixes: d785ed945de6 ("net: wwan: t7xx: PCIe reset rescan")
>>
>> The completion waiting was introduced in a different commit. I 
>> believe, the fix tag should be 13e920d93e37 ("net: wwan: t7xx: Add 
>> core components")
>>
> 
> Got it.

[...]

> Yes, the patch works fine, needs some minor modifications, could we 
> feedback to the driver author to merge these changes.

Looks like the drivers authors haven't enough time to maintain it. You 
are the most active developer at the moment. Could formally resend the 
updated patch with refcounter as V3? And, I believe, we can apply it.

--
Sergey