[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4cfc85af-c13a-aa9c-a57c-bf4b6e0f2186@trinnet.net>
Date: Mon, 9 Jun 2025 16:30:52 -0700
From: David Ranch <linux-hams@...nnet.net>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Denis Arefev <arefev@...mel.ru>, "David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>,
Simon Horman <horms@...nel.org>, Nikita Marushkin <hfggklm@...il.com>,
Ilya Shchipletsov <rabbelkin@...l.ru>,
Hongbo Li <lihongbo22@...wei.com>, linux-hams@...r.kernel.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
lvc-project@...uxtesting.org, stable@...r.kernel.org,
syzbot+ccdfb85a561b973219c7@...kaller.appspotmail.com
Subject: Re: [PATCH net] netrom: fix possible deadlock in nr_rt_device_down
That's unclear to me but maybe someone else knowing the code better than
myself can chime in. I have to assume having these locks present
are for a reason.
--David
KI6ZHD
On 06/09/2025 04:26 PM, Jakub Kicinski wrote:
> On Mon, 9 Jun 2025 16:16:32 -0700 David Ranch wrote:
>> I'm not sure what you mean by "the only user of this code". There are
>> many people using the Linux AX.25 + NETROM stack but we unfortunately
>> don't have a active kernel maintainer for this code today.
>
> Alright, sorry. Either way - these locks are not performance critical
> for you, right?
>
Powered by blists - more mailing lists