From: Kees Cook <kees@kernel.org>
To: Nilay Shroff <nilay@linux.ibm.com>
Cc: "Nathan Chancellor" <nathan@kernel.org>,
"Thomas Weißschuh" <linux@weissschuh.net>,
"Yury Norov" <yury.norov@gmail.com>,
"Qing Zhao" <qing.zhao@oracle.com>,
linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org,
"gjoyce@linux.ibm.com" <gjoyce@linux.ibm.com>
Subject: Re: [PATCH] fortify: Hide run-time copy size from value range tracking
Date: Fri, 13 Dec 2024 16:47:23 -0800 [thread overview]
Message-ID: <202412131646.54417C4E6@keescook> (raw)
In-Reply-To: <3fa35755-f822-4a54-b8fb-4fdc16579c2f@linux.ibm.com>
On Fri, Dec 13, 2024 at 02:49:20PM +0530, Nilay Shroff wrote:
> ./include/linux/fortify-string.h:620:63: error: void value not ignored as it ought to be
Whoops! Thanks, I had only spot-checked padata.o :( I will fix this up
and send a v2.
--
Kees Cook
prev parent reply other threads:[~2024-12-14 0:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 2:09 [PATCH] fortify: Hide run-time copy size from value range tracking Kees Cook
2024-12-13 9:19 ` Nilay Shroff
2024-12-14 0:47 ` Kees Cook [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=202412131646.54417C4E6@keescook \
--to=kees@kernel.org \
--cc=gjoyce@linux.ibm.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=nathan@kernel.org \
--cc=nilay@linux.ibm.com \
--cc=qing.zhao@oracle.com \
--cc=yury.norov@gmail.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