From: "Arnd Bergmann" <arnd@kernel.org>
To: "Kees Cook" <keescook@chromium.org>
Cc: "Brian King" <brking@us.ibm.com>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
"Nathan Chancellor" <nathan@kernel.org>,
"Nick Desaulniers" <ndesaulniers@google.com>,
"James Bottomley" <James.Bottomley@steeleye.com>,
"Damien Le Moal" <damien.lemoal@opensource.wdc.com>,
"Arnd Bergmann" <arnd@arndb.de>,
"Niklas Cassel" <niklas.cassel@wdc.com>,
"John Garry" <john.g.garry@oracle.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev
Subject: Re: [PATCH] [v2] scsi: ipr: work around fortify-string warning
Date: Tue, 14 Feb 2023 22:53:14 +0100 [thread overview]
Message-ID: <85de69eb-5d71-4b29-ba83-c0258d58b807@app.fastmail.com> (raw)
In-Reply-To: <63ec01f0.170a0220.94c76.011e@mx.google.com>
On Tue, Feb 14, 2023, at 22:49, Kees Cook wrote:
> On Tue, Feb 14, 2023 at 02:28:08PM +0100, Arnd Bergmann wrote:
>> From: Arnd Bergmann <arnd@arndb.de>
>>
>> The ipr_log_vpd_compact() function triggers a fortified memcpy() warning
>> about a potential string overflow with all versions of clang:
>
> Perhaps this is arch or config specific? I haven't been able to reproduce
> this for some reason.
I saw it on three arm32 randconfig builds out
of a few thousand, with clang-15, clang-16 and
clang-17. See [1] for one config that triggered
it with recent linux-next based tree.
Arnd
[1] https://pastebin.com/c9FEjzKe
next prev parent reply other threads:[~2023-02-14 21:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 13:28 Arnd Bergmann
2023-02-14 21:49 ` Kees Cook
2023-02-14 21:53 ` Arnd Bergmann [this message]
2023-02-15 4:42 ` Damien Le Moal
2023-02-15 21:32 ` Kees Cook
2023-02-21 19:37 ` Brian King
2023-02-21 23:30 ` Martin K. Petersen
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=85de69eb-5d71-4b29-ba83-c0258d58b807@app.fastmail.com \
--to=arnd@kernel.org \
--cc=James.Bottomley@steeleye.com \
--cc=arnd@arndb.de \
--cc=brking@us.ibm.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=jejb@linux.ibm.com \
--cc=john.g.garry@oracle.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=martin.petersen@oracle.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=niklas.cassel@wdc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®