Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751445AbdFENey (ORCPT ); Mon, 5 Jun 2017 09:34:54 -0400 Received: from mail-it0-f49.google.com ([209.85.214.49]:35499 "EHLO mail-it0-f49.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751295AbdFENee (ORCPT ); Mon, 5 Jun 2017 09:34:34 -0400 Message-ID: <1496669671.343.5.camel@gmail.com> Subject: Re: linux-next: build failure after merge of the akpm-current tree From: Daniel Micay To: Stephen Rothwell , Andrew Morton Cc: Linux-Next Mailing List , Linux Kernel Mailing List , Kees Cook Date: Mon, 05 Jun 2017 09:34:31 -0400 In-Reply-To: <1496667976.343.3.camel@gmail.com> References: <20170605170117.6a1fc15e@canb.auug.org.au> <1496667976.343.3.camel@gmail.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.24.2 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 749 Lines: 13 > It also probably finds more architecture-specific issues and may need > compatibility fixes for them. I could mark it as compatible with only > arm64 and x86(_64) since they're what I've tested to build and work at > runtime and the compile-time errors could be turned into warnings for > now, if it's mandatory that FORTIFY_SOURCE=y doesn't find problems at > compile-time anywhere. If it's a warning, it will still catch the > issue > at runtime like the rest where the size isn't a constant. I'm already leaving out intra-object overflow checks and the alloc_size attributes in this initial submission to make it easier to land so scaling it back a bit more (errors -> warnings, gating on archs) isn't a problem if it's needed to get started.