linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Francis Laniel <laniel_francis@privacyrequired.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-hardening@vger.kernel.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, dja@axtens.net
Subject: Re: [PATCH v6 0/5] Fortify strscpy()
Date: Fri, 20 Nov 2020 11:52:07 -0800	[thread overview]
Message-ID: <202011201150.AE57F56EB@keescook> (raw)
In-Reply-To: <5676804.6kI0aEeX2c@machine>

On Fri, Nov 20, 2020 at 10:40:38AM +0100, Francis Laniel wrote:
> Le vendredi 20 novembre 2020, 02:35:43 CET Andrew Morton a écrit :
> > On Thu, 19 Nov 2020 17:49:10 +0100 laniel_francis@privacyrequired.com wrote:
> > > This patch set answers to this issue:
> > > https://github.com/KSPP/linux/issues/46
> > 
> > I fail to understand what this patchset has to do with that
> > one-element-array issue :(
>
> I think I linked another issue totally not related with that one...

This just looks like a typo. The URL should be:
https://github.com/KSPP/linux/issues/96

-- 
Kees Cook


  parent reply	other threads:[~2020-11-20 19:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20201119164915.10618-1-laniel_francis@privacyrequired.com>
2020-11-20  1:35 ` [PATCH v6 0/5] Fortify strscpy() Andrew Morton
2020-11-20 13:33   ` David Laight
2020-11-20 15:51     ` Francis Laniel
     [not found]   ` <5676804.6kI0aEeX2c@machine>
2020-11-20 19:52     ` Kees Cook [this message]
     [not found] ` <20201119164915.10618-2-laniel_francis@privacyrequired.com>
2020-11-20  1:38   ` [PATCH v6 1/5] string.h: detect intra-object overflow in fortified string functions Andrew Morton
2020-11-20  9:41     ` Francis Laniel

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=202011201150.AE57F56EB@keescook \
    --to=keescook@chromium.org \
    --cc=akpm@linux-foundation.org \
    --cc=dja@axtens.net \
    --cc=laniel_francis@privacyrequired.com \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    /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;
as well as URLs for NNTP newsgroup(s).