[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190222072652.2441e8a2@canb.auug.org.au>
Date: Fri, 22 Feb 2019 07:26:52 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Kees Cook <keescook@...omium.org>
Cc: "Tobin C. Harding" <me@...in.cc>, Jann Horn <jannh@...gle.com>, "Tobin
C. Harding" <tobin@...nel.org>, Shuah Khan <shuah@...nel.org>, Alexander
Shishkin <alexander.shishkin@...ux.intel.com>, Greg Kroah-Hartman
<gregkh@...uxfoundation.org>, Andy Shevchenko
<andriy.shevchenko@...ux.intel.com>, Kernel Hardening
<kernel-hardening@...ts.openwall.com>, kernel list
<linux-kernel@...r.kernel.org>, Andy Lutomirski <luto@...capital.net>,
Rasmus Villemoes <linux@...musvillemoes.dk>, Daniel Micay
<danielmicay@...il.com>, Arnd Bergmann <arnd@...db.de>, Miguel Ojeda
<miguel.ojeda.sandonis@...il.com>, "Gustavo A. R. Silva"
<gustavo@...eddedor.com>
Subject: Re: [PATCH 5/6] lib: Fix function documentation for
strncpy_from_user
Hi Kees,
On Wed, 20 Feb 2019 22:02:32 -0800 Kees Cook <keescook@...omium.org> wrote:
>
> What I can't quite figure out yet is how to find a way for sfr to flag
> newly added users of strcpy, strncpy, and strlcpy. We might need to
> bring back __deprecated, but hide it behind a W=linux-next flag or
> something crazy. Stephen, in your builds you're already injecting
> -Wimplicit-fallthrough: do you do W=1 or anything like that? If not, I
> think we need some W= setting for your linux-next builds that generate
> the maintainer-nag warnings...
I just have a set of compiler flags that my build scripts explicitly
enable by setting KCFLAGS.
--
Cheers,
Stephen Rothwell
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
