From: hadess <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] fd0161: hci-tester: Work-around possible string overflow
Date: Tue, 16 Jun 2026 05:19:54 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1112149/000000-fd0161@github.com> (raw)
Branch: refs/heads/1112149
Home: https://github.com/bluez/bluez
Commit: fd0161f8f6af60019a11b003772a5655ae05c632
https://github.com/bluez/bluez/commit/fd0161f8f6af60019a11b003772a5655ae05c632
Author: Bastien Nocera <hadess@hadess.net>
Date: 2026-06-16 (Tue, 16 Jun 2026)
Changed paths:
M tools/hci-tester.c
Log Message:
-----------
hci-tester: Work-around possible string overflow
Quiet overflow warning by checking for a non-NULL destination.
In function 'memcpy',
inlined from 'test_pre_setup_lt_address' at tools/hci-tester.c:67:2:
/usr/include/bits/string_fortified.h:29:10: warning: '__builtin_memcpy' writing 6 bytes into a region of size 0 overflows the destination [-Wstringop-overflow=]
29 | return __builtin___memcpy_chk (__dest, __src, __len,
| ^
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-06-16 12:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bluez/bluez/push/refs/heads/1112149/000000-fd0161@github.com \
--to=noreply@github.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 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.