From: Francis Laniel <laniel_francis@privacyrequired.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-hardening@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, dja@axtens.net,
keescook@chromium.org, Daniel Micay <danielmicay@gmail.com>
Subject: Re: [PATCH v6 1/5] string.h: detect intra-object overflow in fortified string functions
Date: Fri, 20 Nov 2020 10:41:45 +0100 [thread overview]
Message-ID: <2634935.IsWps63H46@machine> (raw)
In-Reply-To: <20201119173822.779c253bd946f7da30155cc8@linux-foundation.org>
Le vendredi 20 novembre 2020, 02:38:22 CET Andrew Morton a écrit :
> On Thu, 19 Nov 2020 17:49:11 +0100 laniel_francis@privacyrequired.com wrote:
> > From: Daniel Axtens <dja@axtens.net>
> >
> > ...
> >
> > Cc: Daniel Micay <danielmicay@gmail.com>
> > Cc: Kees Cook <keescook@chromium.org>
> > Reviewed-by: Kees Cook <keescook@chromium.org>
> > Signed-off-by: Daniel Axtens <dja@axtens.net>
>
> This patch should have your signoff as well, as per
> Documentation/process/submitting-patches.rst "Developer's Certificate
> of Origin 1.1".
>
> I think it would be best to send out a v7 to address this and the cover
> letter issue, please.
Will be done for the v7!
I just read the documentation page, rebase on Linus Torvalds tree and send the
v7!
next prev parent reply other threads:[~2020-11-20 9:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 16:49 [PATCH v6 0/5] Fortify strscpy() laniel_francis
2020-11-19 16:49 ` [PATCH v6 1/5] string.h: detect intra-object overflow in fortified string functions laniel_francis
2020-11-20 1:38 ` Andrew Morton
2020-11-20 9:41 ` Francis Laniel [this message]
2020-11-19 16:49 ` [PATCH v6 2/5] lkdtm: tests for FORTIFY_SOURCE laniel_francis
2020-11-19 16:49 ` [PATCH v6 3/5] string.h: Add FORTIFY coverage for strscpy() laniel_francis
2020-11-19 16:49 ` [PATCH v6 4/5] Add new file in LKDTM to test fortified strscpy laniel_francis
2020-11-19 16:49 ` [PATCH v6 5/5] Correct wrong filenames in comment laniel_francis
2020-11-20 1:35 ` [PATCH v6 0/5] Fortify strscpy() Andrew Morton
2020-11-20 9:40 ` Francis Laniel
2020-11-20 19:52 ` Kees Cook
2020-11-22 16:28 ` Francis Laniel
2020-11-20 13:33 ` David Laight
2020-11-20 15:51 ` 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=2634935.IsWps63H46@machine \
--to=laniel_francis@privacyrequired.com \
--cc=akpm@linux-foundation.org \
--cc=danielmicay@gmail.com \
--cc=dja@axtens.net \
--cc=keescook@chromium.org \
--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).