From: duoming@zju.edu.cn
To: "Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>
Cc: linux-kernel@vger.kernel.org, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
gregkh@linuxfoundation.org, alexander.deucher@amd.com,
broonie@kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net] NFC: hci: fix sleep in atomic context bugs in nfc_hci_hcp_message_tx
Date: Mon, 16 May 2022 18:18:45 +0800 (GMT+08:00) [thread overview]
Message-ID: <6aba1413.196eb.180cc609bf1.Coremail.duoming@zju.edu.cn> (raw)
In-Reply-To: <d5fdfe27-a6de-3030-ce51-9f4f45d552f3@linaro.org>
Hello,
On Mon, 16 May 2022 08:44:39 +0200 Krzysztof wrote:
> > There are sleep in atomic context bugs when the request to secure
> > element of st21nfca is timeout. The root cause is that kzalloc and
> > alloc_skb with GFP_KERNEL parameter is called in st21nfca_se_wt_timeout
> > which is a timer handler. The call tree shows the execution paths that
> > could lead to bugs:
> >
> > (Interrupt context)
> > st21nfca_se_wt_timeout
> > nfc_hci_send_event
> > nfc_hci_hcp_message_tx
> > kzalloc(..., GFP_KERNEL) //may sleep
> > alloc_skb(..., GFP_KERNEL) //may sleep
> >
> > This patch changes allocation mode of kzalloc and alloc_skb from
> > GFP_KERNEL to GFP_ATOMIC in order to prevent atomic context from
> > sleeping. The GFP_ATOMIC flag makes memory allocation operation
> > could be used in atomic context.
> >
> > Fixes: 8b8d2e08bf0d ("NFC: HCI support")
> > Signed-off-by: Duoming Zhou <duoming@zju.edu.cn>
> > ---
> > net/nfc/hci/hcp.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/net/nfc/hci/hcp.c b/net/nfc/hci/hcp.c
> > index 05c60988f59..1caf9c2086f 100644
> > --- a/net/nfc/hci/hcp.c
> > +++ b/net/nfc/hci/hcp.c
> > @@ -30,7 +30,7 @@ int nfc_hci_hcp_message_tx(struct nfc_hci_dev *hdev, u8 pipe,
> > int hci_len, err;
> > bool firstfrag = true;
> >
> > - cmd = kzalloc(sizeof(struct hci_msg), GFP_KERNEL);
> > + cmd = kzalloc(sizeof(*cmd), GFP_ATOMIC);
>
> No, this does not look correct. This function can sleep, so it can use
> GFP_KERNEL. Please just look at the function before replacing any flags...
I am sorry, I don`t understand why nfc_hci_hcp_message_tx() can sleep.
I think st21nfca_se_wt_timeout() is a timer handler, which is in interrupt context.
The call tree shows the execution paths that could lead to bugs:
st21nfca_hci_se_io()
mod_timer(&info->se_info.bwi_timer,...)
st21nfca_se_wt_timeout() //timer handler, interrupt context
nfc_hci_send_event()
nfc_hci_hcp_message_tx()
kzalloc(..., GFP_KERNEL) //may sleep
alloc_skb(..., GFP_KERNEL) //may sleep
What`s more, I think the "mutex_lock(&hdev->msg_tx_mutex)" called by nfc_hci_hcp_message_tx()
is also improper.
Please correct me, If you think I am wrong. Thanks for your time.
Best regards,
Duoming Zhou
next prev parent reply other threads:[~2022-05-16 10:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 2:10 Duoming Zhou
2022-05-16 6:44 ` Krzysztof Kozlowski
2022-05-16 10:18 ` duoming [this message]
2022-05-16 10:43 ` Krzysztof Kozlowski
2022-05-17 10:56 ` duoming
2022-05-17 11:39 ` Krzysztof Kozlowski
2022-05-17 12:24 ` duoming
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=6aba1413.196eb.180cc609bf1.Coremail.duoming@zju.edu.cn \
--to=duoming@zju.edu.cn \
--cc=alexander.deucher@amd.com \
--cc=broonie@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=krzysztof.kozlowski@linaro.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®