From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: duoming@zju.edu.cn
Cc: linux-kernel@vger.kernel.org, kuba@kernel.org,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
gregkh@linuxfoundation.org, alexander.deucher@amd.com,
broonie@kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net v2] NFC: hci: fix sleep in atomic context bugs in nfc_hci_hcp_message_tx
Date: Wed, 18 May 2022 11:39:27 +0200 [thread overview]
Message-ID: <bb566eb7-c571-9a51-af51-78e36412fbfc@linaro.org> (raw)
In-Reply-To: <454a29ba.1b9b1.180d576985b.Coremail.duoming@zju.edu.cn>
On 18/05/2022 06:39, duoming@zju.edu.cn wrote:
>> There is.
>>
>> nfc_hci_failure -> spin lock -> nfc_driver_failure -> nfc_targets_found
>> -> device_lock
>>
>> I found it just by a very quick look, so I suspect there are several
>> other places, not really checked.
>
> I agree with you, the spin_lock is not a good solution to this problem. There is another solution:
>
> We could put the nfc_hci_send_event() of st21nfca_se_wt_timeout() in a work item, then, using
> schedule_work() in st21nfca_se_wt_timeout() to execute the work item. The schedule_work() will
> wake up another kernel thread which is in process context to execute the bottom half of the interrupt,
> so it allows sleep.
>
> The following is the details.
Yes, this seems good solution. You might also need to add
cancel_work_sync to all places removing the timer.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-05-18 9:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 10:55 Duoming Zhou
2022-05-17 11:42 ` Krzysztof Kozlowski
2022-05-17 15:25 ` duoming
2022-05-17 15:28 ` Krzysztof Kozlowski
2022-05-18 4:39 ` duoming
2022-05-18 9:39 ` Krzysztof Kozlowski [this message]
2022-05-18 11:05 ` duoming
2022-05-18 11:43 ` Krzysztof Kozlowski
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=bb566eb7-c571-9a51-af51-78e36412fbfc@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=alexander.deucher@amd.com \
--cc=broonie@kernel.org \
--cc=davem@davemloft.net \
--cc=duoming@zju.edu.cn \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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®