mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Ivan Pravdin <ipravdin.official@gmail.com>
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
	luiz.dentz@gmail.com, linux-bluetooth@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	syzbot+ac3c79181f6aecc5120c@syzkaller.appspotmail.com
Subject: Re: [PATCH v2] Bluetooth: coredump: Use tmp buffer with dev_coredumpv
Date: Wed, 16 Jul 2025 05:06:38 +0200	[thread overview]
Message-ID: <d8a85b98-4c70-4fcf-9d7b-bd1de2d780c3@molgen.mpg.de> (raw)
In-Reply-To: <20250716003726.124975-2-ipravdin.official@gmail.com>

Dear Ivan,


Thank you for your patch and fixing the report.

Am 16.07.25 um 02:37 schrieb Ivan Pravdin:

Personally, I’d start with the problem description.

> Create and use new vmalloc'ed buffer with dev_coredumpv. From
> dev_coredumpv documentation:
> 
> `This function takes ownership of the vmalloc'ed data and will free
> it when it is no longer used.`

You could use email/Markdown style citation by prepending the lines with 
`> `.

> As hdev->dump is used after dev_coredumpv, create temporary buffer to
> hold hdev->dump data.
> 
> Reported-by: syzbot+ac3c79181f6aecc5120c@syzkaller.appspotmail.com
> Closes: https://lore.kernel.org/all/67eaa688.050a0220.1547ec.014a.GAE@google.com

Add a trace excerpt to the commit message?

> Fixes: b257e02ecc46 ("HCI: coredump: Log devcd dumps into the monitor")
> Signed-off-by: Ivan Pravdin <ipravdin.official@gmail.com>
> ---
> v1 -> v2: Changed subject prefix to Bluetooth:
> 
>   net/bluetooth/coredump.c | 7 ++++++-
>   1 file changed, 6 insertions(+), 1 deletion(-)
> 
> diff --git a/net/bluetooth/coredump.c b/net/bluetooth/coredump.c
> index 819eacb38762..1232c9a94f95 100644
> --- a/net/bluetooth/coredump.c
> +++ b/net/bluetooth/coredump.c
> @@ -243,6 +243,7 @@ static void hci_devcd_handle_pkt_pattern(struct hci_dev *hdev,
>   static void hci_devcd_dump(struct hci_dev *hdev)
>   {
>   	struct sk_buff *skb;
> +	char *coredump;
>   	u32 size;
>   
>   	bt_dev_dbg(hdev, "state %d", hdev->dump.state);
> @@ -250,7 +251,11 @@ static void hci_devcd_dump(struct hci_dev *hdev)
>   	size = hdev->dump.tail - hdev->dump.head;
>   
>   	/* Emit a devcoredump with the available data */
> -	dev_coredumpv(&hdev->dev, hdev->dump.head, size, GFP_KERNEL);
> +	coredump = vmalloc(size);
> +	if (coredump) {
> +		memcpy(coredump, hdev->dump.head, size);
> +		dev_coredumpv(&hdev->dev, coredump, size, GFP_KERNEL);
> +	}

Should it be logged, if allocation fails?

>   
>   	/* Send a copy to monitor as a diagnostic packet */
>   	skb = bt_skb_alloc(size, GFP_ATOMIC);


Kind regards,

Paul

  reply	other threads:[~2025-07-16  3:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-16  0:37 Ivan Pravdin
2025-07-16  3:06 ` Paul Menzel [this message]
2025-07-17  3:35   ` Ivan Pravdin
2025-07-16 14:11 ` Luiz Augusto von Dentz
2025-07-17  4:11   ` Ivan Pravdin
2025-07-17  5:06     ` Ivan Pravdin

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=d8a85b98-4c70-4fcf-9d7b-bd1de2d780c3@molgen.mpg.de \
    --to=pmenzel@molgen.mpg.de \
    --cc=ipravdin.official@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=syzbot+ac3c79181f6aecc5120c@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®