Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] API replacement/deprecation

[Kees Cook <keescook@chromium.org>]

On Thu, Sep 6, 2018 at 4:18 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Kees,
>
> On Thu, 6 Sep 2018 11:24:11 -0700 Kees Cook <keescook@chromium.org> wrote:
>>
>> If there was an agreement by all maintainers that deprecated
>> functions/patterns should not be added, and we documented the
>> deprecation somewhere like Documentation/process/deprecated.rst, then
>> we could make the declaration that if such functions got added (it's
>> easy to mechanically check for them), it would be the responsibility
>> of the author and maintainer chain to see that it got fixed before the
>> release is cut. We already have this for things like "breaks the x86
>> allmodconfig build" or similar. The checking would be manual, and the
>> enforcement would be by agreement, but it'd be better than the kind of
>> "please don't do this" hand-waving we've had in the past.
>
> I could do this in linux-next, of course, the same way I check for
> missing signed-off-bys.  All I would need is the list of deprecated
> things.

Hopefully we can all agree on deprecating strcpy() and strncpy() in
favor of strscpy()?

-Kees

-- 
Kees Cook
Pixel Security