From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.5 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_PASS,URIBL_BLOCKED,USER_AGENT_GIT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4DD6AC43441 for ; Mon, 26 Nov 2018 10:55:03 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id DD0FF21473 for ; Mon, 26 Nov 2018 10:55:02 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=kernel.org header.i=@kernel.org header.b="a62xX8ho" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org DD0FF21473 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=linuxfoundation.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727716AbeKZVso (ORCPT ); Mon, 26 Nov 2018 16:48:44 -0500 Received: from mail.kernel.org ([198.145.29.99]:57388 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726708AbeKZVso (ORCPT ); Mon, 26 Nov 2018 16:48:44 -0500 Received: from localhost (5356596B.cm-6-7b.dynamic.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 541D92146F; Mon, 26 Nov 2018 10:54:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1543229699; bh=UdZX2wAHl3VbvzZjqRrx0YFuV2hFJEqv+Xc6NcOWtfY=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=a62xX8hoFBp6uSj9f77tIWUjymllG0+FFr21dzxi0XgqFAGnfJCMAVBv4DuAZQ9Ve chRQHLx86qtO9KncxWv785jNjR0SU+0Z3muqCykZ7OSqKQxAIirTsexzk7/Azi4IYe InL6VQR6beXUQWwQ7fDjEB2IRQT9wfEaSvlRTJG8= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, kbuild test robot , Matthias Kaehlcke , Arnd Bergmann , Bernhard.Rosenkranzer@linaro.org, Greg Hackmann , Kees Cook , Linus Torvalds , Masahiro Yamada , Michael Davidson , Nick Desaulniers , Peter Zijlstra , Stephen Hines , Thomas Gleixner , dianders@chromium.org, Ingo Molnar , Nathan Chancellor Subject: [PATCH 4.4 37/70] x86/build: Use cc-option to validate stack alignment parameter Date: Mon, 26 Nov 2018 11:50:52 +0100 Message-Id: <20181126105050.333718174@linuxfoundation.org> X-Mailer: git-send-email 2.19.2 In-Reply-To: <20181126105046.722096341@linuxfoundation.org> References: <20181126105046.722096341@linuxfoundation.org> User-Agent: quilt/0.65 X-stable: review MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 4.4-stable review patch. If anyone has any objections, please let me know. ------------------ From: Matthias Kaehlcke commit 9e8730b178a2472fca3123e909d6e69cc8127778 upstream. With the following commit: 8f91869766c0 ("x86/build: Fix stack alignment for CLang") cc-option is only used to determine the name of the stack alignment option supported by the compiler, but not to verify that the actual parameter