From: patchwork-bot+bluetooth@kernel.org
To: Celeste Liu <coelacanthushex@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, CoelacanthusHex@gmail.com
Subject: Re: [PATCH bluez v3] monitor: fix buffer overflow when terminal width > 255
Date: Tue, 17 Sep 2024 14:20:37 +0000 [thread overview]
Message-ID: <172658283749.155805.6387894003374291123.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240917-fix-log-buffer-overflow-v3-1-26fd441bb7df@gmail.com>
Hello:
This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 17 Sep 2024 14:30:46 +0800 you wrote:
> In current code, we create line buffer with size 256, which can contains
> 255 ASCII characters. But in modern system, terminal can have larger
> width. It may cause buffer overflow in snprintf() text.
>
> limits.h provides constant LINE_MAX.
>
> {LINE_MAX}
> Unless otherwise noted, the maximum length, in bytes, of a
> utility's input line (either standard input or another
> file), when the utility is described as processing text
> files. The length includes room for the trailing <newline>.
> Minimum Acceptable Value: {_POSIX2_LINE_MAX}
>
> [...]
Here is the summary with links:
- [bluez,v3] monitor: fix buffer overflow when terminal width > 255
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=2908491c7efe
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:[~2024-09-17 14:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-17 6:30 [PATCH bluez v3] monitor: fix buffer overflow when terminal width > 255 Celeste Liu
2024-09-17 8:09 ` [bluez,v3] " bluez.test.bot
2024-09-17 14: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=172658283749.155805.6387894003374291123.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=coelacanthushex@gmail.com \
--cc=linux-bluetooth@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