From: patchwork-bot+bluetooth@kernel.org
To: Ajith P V <ajithpv.linux@gmail.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: bnep: refactor deprecated strcpy
Date: Tue, 11 Aug 2026 20:10:17 +0000 [thread overview]
Message-ID: <178647901788.1134064.15151706764322926988.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260811094932.86448-1-ajithpv.linux@gmail.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 11 Aug 2026 09:49:32 +0000 you wrote:
> The strcpy() function is deprecated across the kernel tree and
> moving towards complete elimination. It provides no verification
> limits against buffer overflows and does not guarantee strict boundary
> restrictions [1][2].
>
> Replace instances of strcpy() in `net/bluetooth/bnep/core.c` with the safer
> strscpy() alternative. Since both target destination blocks are
> statically allocated fixed-size arrays within their structure definitions,
> leverage the compile time sizeof() operator to explicitly pass the
> destination buffer capacities.
>
> [...]
Here is the summary with links:
- Bluetooth: bnep: refactor deprecated strcpy
https://git.kernel.org/bluetooth/bluetooth-next/c/6d5e3062ef68
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-08-11 20:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 9:49 [PATCH] Bluetooth: bnep: refactor deprecated strcpy Ajith P V
2026-08-11 11:05 ` bluez.test.bot
2026-08-11 20:10 ` patchwork-bot+bluetooth [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=178647901788.1134064.15151706764322926988.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=ajithpv.linux@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.