From: Kees Cook <keescook@chromium.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Christian Lamparter <chunkeey@gmail.com>,
Arnd Bergmann <arnd@kernel.org>, Kalle Valo <kvalo@kernel.org>,
Johannes Berg <johannes.berg@intel.com>,
Shiji Yang <yangshiji66@outlook.com>,
Nick Kossifidis <mickflemm@gmail.com>,
Jiri Slaby <jirislaby@kernel.org>,
Christian Marangi <ansuelsmth@gmail.com>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] carl9170: re-fix fortified-memset warning
Date: Fri, 23 Jun 2023 16:33:45 -0700 [thread overview]
Message-ID: <202306231607.8632EBE15@keescook> (raw)
In-Reply-To: <24986b5e-5cd1-4cd5-aff3-b5eab2c0fdde@app.fastmail.com>
On Fri, Jun 23, 2023 at 06:05:57PM +0200, Arnd Bergmann wrote:
> Doing the randconfig builds with the latest compilers, carl9170 is the
> only one I see with fortified-string warnings, and there are a few
> dozen other drivers that I see with W=1, including one that affects
> all wireless drivers.
Can you post the config that triggers this? I can't reproduce this
warning...
-Kees
--
Kees Cook
next prev parent reply other threads:[~2023-06-23 23:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 15:23 [PATCH 1/2] carl9170: re-fix fortified-memset warning Arnd Bergmann
2023-06-23 15:24 ` [PATCH 2/2] mac80211: make ieee80211_tx_info padding explicit Arnd Bergmann
2023-06-23 23:07 ` Kees Cook
2023-06-23 15:38 ` [PATCH 1/2] carl9170: re-fix fortified-memset warning Christian Lamparter
2023-06-23 16:05 ` Arnd Bergmann
2023-06-23 17:15 ` Christian Lamparter
2023-06-26 6:51 ` Jiri Slaby
2023-06-23 23:33 ` Kees Cook [this message]
2023-06-23 23:04 ` 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=202306231607.8632EBE15@keescook \
--to=keescook@chromium.org \
--cc=ansuelsmth@gmail.com \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=chunkeey@gmail.com \
--cc=jirislaby@kernel.org \
--cc=johannes.berg@intel.com \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mickflemm@gmail.com \
--cc=yangshiji66@outlook.com \
/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.