From: patchwork-bot+bluetooth@kernel.org
To: Kees Cook <kees@kernel.org>
Cc: stable@vger.kernel.org, lkp@intel.com, marcel@holtmann.org,
luiz.dentz@gmail.com, jpoimboe@kernel.org, nathan@kernel.org,
peterz@infradead.org, linux-bluetooth@vger.kernel.org,
morbo@google.com, justinstitt@google.com, mmandlik@google.com,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: vhci: Avoid needless snprintf() calls
Date: Tue, 15 Apr 2025 20:20:41 +0000 [thread overview]
Message-ID: <174474844125.2765712.8238252106715217698.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250415161518.work.889-kees@kernel.org>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 15 Apr 2025 09:15:19 -0700 you wrote:
> Avoid double-copying of string literals. Use a "const char *" for each
> string instead of copying from .rodata into stack and then into the skb.
> We can go directly from .rodata to the skb.
>
> This also works around a Clang bug (that has since been fixed[1]).
>
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202401250927.1poZERd6-lkp@intel.com/
> Fixes: ab4e4380d4e1 ("Bluetooth: Add vhci devcoredump support")
> Link: https://github.com/llvm/llvm-project/commit/ea2e66aa8b6e363b89df66dc44275a0d7ecd70ce [1]
> Cc: stable@vger.kernel.org
> Signed-off-by: Kees Cook <kees@kernel.org>
>
> [...]
Here is the summary with links:
- Bluetooth: vhci: Avoid needless snprintf() calls
https://git.kernel.org/bluetooth/bluetooth-next/c/3b32759328e9
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:[~2025-04-15 20:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 16:15 [PATCH] Bluetooth: vhci: Avoid needless snprintf() calls Kees Cook
2025-04-15 16:19 ` Nathan Chancellor
2025-04-15 16:29 ` Josh Poimboeuf
2025-04-15 17:04 ` bluez.test.bot
2025-04-15 17:16 ` Kees Cook
2025-04-15 19:11 ` Luiz Augusto von Dentz
2025-04-15 20:20 ` 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=174474844125.2765712.8238252106715217698.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=jpoimboe@kernel.org \
--cc=justinstitt@google.com \
--cc=kees@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=mmandlik@google.com \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=peterz@infradead.org \
--cc=stable@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox