From: Andrew Morton <akpm@linux-foundation.org>
To: Kees Cook <keescook@chromium.org>
Cc: linux-kernel@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>,
Daniel Micay <danielmicay@gmail.com>
Subject: Re: [PATCH 0/7] CONFIG_FORTIFY_SOURCE
Date: Mon, 19 Jun 2017 14:50:49 -0700 [thread overview]
Message-ID: <20170619145049.38dc14030059786ef6ca6a54@linux-foundation.org> (raw)
In-Reply-To: <1497903987-21002-1-git-send-email-keescook@chromium.org>
On Mon, 19 Jun 2017 13:26:20 -0700 Kees Cook <keescook@chromium.org> wrote:
> Here are the outstanding fixes for CONFIG_FORTIFY_SOURCE, along with Daniel's
> v5 patch and a tweak from me to add CONFIG_ARCH_HAS_FORTIFY_SOURCE to avoid
> failing the build on architectures that have not hunted down all the needed
> fixes yet.
>
> This was in my for-next/kspp tree, but since it depends on fixes in other
> trees, the preference is for these to all get carried in -mm instead of
> in KSPP.
All the patches you sent are already in -next (from the kspp tree?) so
I can't use them.
> The extra needed fixes in -next are:
>
> scsi: csiostor: Avoid content leaks and casts
> arm64, vdso: Define vdso_{start,end} as array
> staging/rts5208: Fix read overflow in memcpy
> libertas: Avoid reading past end of buffer
> ray_cs: Avoid reading past end of buffer
These didn't get sent out?
If the kspp tree is already in -next then how about leaving things that
way, and send Linus a pull request for -rc1?
next prev parent reply other threads:[~2017-06-19 21:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-19 20:26 [PATCH 0/7] CONFIG_FORTIFY_SOURCE Kees Cook
2017-06-19 20:26 ` [PATCH 1/7] efi: Avoid fortify checks in EFI stub Kees Cook
2017-06-19 20:26 ` [PATCH 2/7] x86/power/64: Use char arrays for asm function names Kees Cook
2017-06-19 20:26 ` [PATCH 3/7] kexec_file: Adjust declaration of kexec_purgatory Kees Cook
2017-06-19 20:26 ` [PATCH 4/7] IB/rxe: Do not copy extra stack memory to skb Kees Cook
2017-06-19 20:26 ` [PATCH 5/7] powerpc: Don't fortify prom_init Kees Cook
2017-06-19 20:26 ` [PATCH 6/7] powerpc: Make feature-fixup tests fortify-safe Kees Cook
2017-06-19 20:26 ` [PATCH 7/7] include/linux/string.h: add the option of fortified string.h functions Kees Cook
2017-09-10 10:55 ` Geert Uytterhoeven
2017-09-10 13:51 ` Arnd Bergmann
2017-06-19 21:50 ` Andrew Morton [this message]
2017-06-19 22:12 ` [PATCH 0/7] CONFIG_FORTIFY_SOURCE Kees Cook
2017-06-19 22:31 ` Andrew Morton
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=20170619145049.38dc14030059786ef6ca6a54@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=danielmicay@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).