From: Arnd Bergmann <arnd@kernel.org>
To: Kees Cook <keescook@chromium.org>
Cc: linux-hardening@vger.kernel.org,
"Toke Høiland-Jørgensen" <toke@toke.dk>,
linux-wireless@vger.kernel.org, "Kalle Valo" <kvalo@kernel.org>,
"Arnd Bergmann" <arnd@arndb.de>
Subject: [PATCH 0/2] wifi: ath: false-positive fortified-memset warnings
Date: Thu, 28 Mar 2024 14:55:03 +0100 [thread overview]
Message-ID: <20240328135509.3755090-1-arnd@kernel.org> (raw)
From: Arnd Bergmann <arnd@arndb.de>
While testing some other patch series I worked on across gcc versions, I found
a couple of stringop warnings that only show up with some toolchains but not
others. The warnings I both seem to be false positive.
I have also not found an explanation why both of these happen in atheros
wireless drivers, as I don't see this in other drivers.
Maybe Kees can work out what is going on here.
Arnd Bergmann (2):
[RESEND] carl9170: re-fix fortified-memset warning
ath9k: work around memset overflow warning
drivers/net/wireless/ath/ath.h | 6 ++++--
drivers/net/wireless/ath/ath9k/main.c | 3 +--
drivers/net/wireless/ath/carl9170/tx.c | 3 ++-
3 files changed, 7 insertions(+), 5 deletions(-)
--
2.39.2
next reply other threads:[~2024-03-28 13:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 13:55 Arnd Bergmann [this message]
2024-03-28 13:55 ` [PATCH 1/2] [RESEND] wifi: carl9170: re-fix fortified-memset warning Arnd Bergmann
2024-03-28 21:51 ` Kees Cook
2024-03-29 12:56 ` Christian Lamparter
2024-04-04 10:10 ` Kalle Valo
2024-03-28 13:55 ` [PATCH 2/2] wifi: ath9k: work around memset overflow warning Arnd Bergmann
2024-03-28 21:14 ` Toke Høiland-Jørgensen
2024-03-28 21:50 ` Kees Cook
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=20240328135509.3755090-1-arnd@kernel.org \
--to=arnd@kernel.org \
--cc=arnd@arndb.de \
--cc=keescook@chromium.org \
--cc=kvalo@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=toke@toke.dk \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).