From: Markus Elfring <Markus.Elfring@web.de>
To: Levi Yun <yeoreum.yun@arm.com>, Yunseong Kim <yskelg@gmail.com>,
linux-bluetooth@vger.kernel.org,
Johan Hedberg <johan.hedberg@gmail.com>,
Luiz Von Dentz <luiz.dentz@gmail.com>,
Marcel Holtmann <marcel@holtmann.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Austin Kim <austindh.kim@gmail.com>,
MichelleJin <shjy180909@gmail.com>,
Levi Yun <ppbuk5246@gmail.com>
Subject: Re: [PATCH] hci: fix double free in hci_req_sync
Date: Tue, 2 Jul 2024 21:40:21 +0200 [thread overview]
Message-ID: <4036b194-3014-4523-b8d0-ea39664607a3@web.de> (raw)
In-Reply-To: <20240701194531.97576-2-yskelg@gmail.com>
…
> +++ b/net/bluetooth/hci_request.c
> @@ -106,8 +106,7 @@ void hci_req_sync_complete(struct hci_dev *hdev, u8 result, u16 opcode,
> hdev->req_result = result;
> hdev->req_status = HCI_REQ_DONE;
> if (skb) {
> - kfree_skb(hdev->req_skb);
> - hdev->req_skb = skb_get(skb);
> + hci_req_skb_release_and_set(hdev, skb_get(skb));
> }
> wake_up_interruptible(&hdev->req_wait_q);
…
How do you think about to omit any curly brackets here?
…
> +++ b/net/bluetooth/hci_request.h
> @@ -28,6 +28,15 @@
>
> #define hci_req_sync_lock(hdev) mutex_lock(&hdev->req_lock)
> #define hci_req_sync_unlock(hdev) mutex_unlock(&hdev->req_lock)
> +#define hci_req_skb_release_and_set(hdev, val) \
> +({ \
> + if (hdev->req_skb) { \
> + spin_lock(&hdev->req_skb_lock); \
> + kfree_skb(hdev->req_skb); \
> + hdev->req_skb = val; \
> + spin_unlock(&hdev->req_skb_lock); \
> + } \
> +})
…
* Do you expect that any data synchronisation should be performed
for the shown pointer check?
* Can it eventually matter to implement such a macro with a statement
like “guard(spinlock)(&hdev->req_skb_lock);”?
https://elixir.bootlin.com/linux/v6.10-rc6/source/include/linux/spinlock.h#L561
Regards,
Markus
prev parent reply other threads:[~2024-07-02 19:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 19:45 Yunseong Kim
2024-07-01 20:06 ` Luiz Augusto von Dentz
2024-07-01 20:14 ` Yunseong Kim
2024-07-02 19:40 ` Markus Elfring [this message]
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=4036b194-3014-4523-b8d0-ea39664607a3@web.de \
--to=markus.elfring@web.de \
--cc=austindh.kim@gmail.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=ppbuk5246@gmail.com \
--cc=shjy180909@gmail.com \
--cc=yeoreum.yun@arm.com \
--cc=yskelg@gmail.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®