From: Jakub Kicinski <kuba@kernel.org>
To: Chengfeng Ye <dg573847474@gmail.com>
Cc: 3chas3@gmail.com, davem@davemloft.net, horms@kernel.org,
linux-atm-general@lists.sourceforge.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] atm: solos-pci: Fix potential deadlock on &cli_queue_lock
Date: Tue, 12 Dec 2023 10:23:04 -0800 [thread overview]
Message-ID: <20231212102304.4f37c828@kernel.org> (raw)
In-Reply-To: <20231207123437.42669-1-dg573847474@gmail.com>
On Thu, 7 Dec 2023 12:34:37 +0000 Chengfeng Ye wrote:
> As &card->cli_queue_lock is acquired under softirq context along the
> following call chain from solos_bh(), other acquisition of the same
> lock inside process context should disable at least bh to avoid double
> lock.
These appear to have been applied to net, thanks!
next prev parent reply other threads:[~2023-12-12 18:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 12:34 [PATCH v3 1/2] atm: solos-pci: Fix potential deadlock on &cli_queue_lock Chengfeng Ye
2023-12-12 18:23 ` Jakub Kicinski [this message]
2023-12-12 18:26 ` Chengfeng Ye
-- strict thread matches above, loose matches on Subject: below --
2023-12-07 12:28 Chengfeng Ye
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=20231212102304.4f37c828@kernel.org \
--to=kuba@kernel.org \
--cc=3chas3@gmail.com \
--cc=davem@davemloft.net \
--cc=dg573847474@gmail.com \
--cc=horms@kernel.org \
--cc=linux-atm-general@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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