From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752659AbdFSVuy (ORCPT ); Mon, 19 Jun 2017 17:50:54 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:53536 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752112AbdFSVuv (ORCPT ); Mon, 19 Jun 2017 17:50:51 -0400 Date: Mon, 19 Jun 2017 14:50:49 -0700 From: Andrew Morton To: Kees Cook Cc: linux-kernel@vger.kernel.org, Stephen Rothwell , Daniel Micay Subject: Re: [PATCH 0/7] CONFIG_FORTIFY_SOURCE Message-Id: <20170619145049.38dc14030059786ef6ca6a54@linux-foundation.org> In-Reply-To: <1497903987-21002-1-git-send-email-keescook@chromium.org> References: <1497903987-21002-1-git-send-email-keescook@chromium.org> X-Mailer: Sylpheed 3.4.1 (GTK+ 2.24.23; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 19 Jun 2017 13:26:20 -0700 Kees Cook 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?