From: David Ranch <linux-hams@trinnet.net>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Denis Arefev <arefev@swemel.ru>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Nikita Marushkin <hfggklm@gmail.com>,
Ilya Shchipletsov <rabbelkin@mail.ru>,
Hongbo Li <lihongbo22@huawei.com>,
linux-hams@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, lvc-project@linuxtesting.org,
stable@vger.kernel.org,
syzbot+ccdfb85a561b973219c7@syzkaller.appspotmail.com
Subject: Re: [PATCH net] netrom: fix possible deadlock in nr_rt_device_down
Date: Mon, 9 Jun 2025 16:30:52 -0700 [thread overview]
Message-ID: <4cfc85af-c13a-aa9c-a57c-bf4b6e0f2186@trinnet.net> (raw)
In-Reply-To: <20250609162642.7cb49915@kernel.org>
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?
>
next prev parent reply other threads:[~2025-06-09 23:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-05 10:54 Denis Arefev
2025-06-09 22:57 ` Jakub Kicinski
[not found] ` <5f821879-6774-3dc2-e97d-e33b76513088@trinnet.net>
2025-06-09 23:26 ` Jakub Kicinski
2025-06-09 23:30 ` David Ranch [this message]
2025-06-10 13:36 ` Dan Cross
2025-06-10 17:00 ` David Ranch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4cfc85af-c13a-aa9c-a57c-bf4b6e0f2186@trinnet.net \
--to=linux-hams@trinnet.net \
--cc=arefev@swemel.ru \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hfggklm@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=lihongbo22@huawei.com \
--cc=linux-hams@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rabbelkin@mail.ru \
--cc=stable@vger.kernel.org \
--cc=syzbot+ccdfb85a561b973219c7@syzkaller.appspotmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®