From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752132AbdFSU0e (ORCPT ); Mon, 19 Jun 2017 16:26:34 -0400 Received: from mail-pf0-f170.google.com ([209.85.192.170]:32803 "EHLO mail-pf0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751037AbdFSU0d (ORCPT ); Mon, 19 Jun 2017 16:26:33 -0400 From: Kees Cook To: Andrew Morton Cc: Kees Cook , linux-kernel@vger.kernel.org, Stephen Rothwell , Daniel Micay Subject: [PATCH 0/7] CONFIG_FORTIFY_SOURCE Date: Mon, 19 Jun 2017 13:26:20 -0700 Message-Id: <1497903987-21002-1-git-send-email-keescook@chromium.org> X-Mailer: git-send-email 2.7.4 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. 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 All the other fixes are already in Linus's tree. -Kees