Received: by 2002:a05:6a10:16a7:0:0:0:0 with SMTP id gp39csp3098742pxb; Mon, 16 Nov 2020 05:54:12 -0800 (PST) X-Google-Smtp-Source: ABdhPJwMRIko7rlpJXRASLVxThBztQFcNCN/AOO8Jqq4FzskQtI8MAPPZE6wzbRM1Uommua+0Uc8 X-Received: by 2002:a17:906:c20f:: with SMTP id d15mr14533189ejz.341.1605534852574; Mon, 16 Nov 2020 05:54:12 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1605534852; cv=none; d=google.com; s=arc-20160816; b=hmta3Qana91UvRnJaWfUZDo2TZ9WhQV0rqPM9rPsnT5pPeayrt/7c0C0veJ0C8HjOp xPVMTsrnEZAGChH8+tx8f9704444JR3Xc2VMsI6mWu1w7A9roug+NpvJUXIxOSa6c7pC +2bhW1ldj/+yVVjVyY3jJ+CsxDgVfryyqdRbTuucGHwutrOU3GpXr55oNLBXhnhg8tAP hvMEZsx3UuezQGJBvzebedmxRC95Ih/spDRB+oru5BZtGnjmRljMXyas8hXGKLDhUXaI evRja4+4A3scT5zmeHOqvNl0mPcZUj9DsMOuEeWTJVaC9jCPdSG/yWLDrvtU4gdQeCgV 1ykA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=Rn/GWbCehAJ+GBDtTEnmHyxU7fKIylPW3sz5YfB6oF4=; b=QOUbMlmA4Q37nA4Ydx1H/mYPyVMDXTAmY6EGnn/4jEOWW/tTnpt3E7CSokV8WsIMVo IhYgnj0BnsKMMsxkQSkJ1BkyPm18v4x7nzkG/K6oFox6AwvXEqlPXgA9lC9ZECMrv17x oN8cIDUW4/sVGvP4dcOX/+1lPNk2KsvrlrHt000y6WiZKrWqrdb8hcQtQ6v4t5C1mc+4 TjwOX4pS/jQRGOS+lgEUECw6Y2b5FkUs2Peg/lb+8koUhKfss2i7RcarDqccOpPo6Sxg ohq1CynlGwrDY1oYFm++CqNDy3BdqDHVh0feGYabhWzaYaO3djZB8qI0yRHEtlgVgSE5 j+qg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=Qd0w7ayR; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id j12si12570084edy.584.2020.11.16.05.53.48; Mon, 16 Nov 2020 05:54:12 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=Qd0w7ayR; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729442AbgKPNvB (ORCPT + 99 others); Mon, 16 Nov 2020 08:51:01 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38446 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728609AbgKPNvA (ORCPT ); Mon, 16 Nov 2020 08:51:00 -0500 Received: from mail-pf1-x444.google.com (mail-pf1-x444.google.com [IPv6:2607:f8b0:4864:20::444]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4220AC0613CF for ; Mon, 16 Nov 2020 05:50:59 -0800 (PST) Received: by mail-pf1-x444.google.com with SMTP id y7so14145510pfq.11 for ; Mon, 16 Nov 2020 05:50:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Rn/GWbCehAJ+GBDtTEnmHyxU7fKIylPW3sz5YfB6oF4=; b=Qd0w7ayRM8p7I/3VxgXVb4Z+J477qPtHJvdhPbVFZ9XwhU7nk+YIXKJu4H/Ta0BwxF t9LBldP1K5XDosLSOw3/pnqneWKXcl2MAT7jJwhpfMGCFjCLG8nlIPEqNH5LXJzKdw4r hr8XIOrGSHOlI22td39a7HRCgRFjfUeDiIH734cDyKiZ68QevmkYAEuchyFDMAuLKEqZ EgO3AZ61AP3smMYLMHfqLFo23PKIeUJ90LOqKZx0qfAplIA9GMZ8oMr+8aX9VJiOh9PE bW5TpM7ui3z/vQ8pnShVeYdJ5P+56IgzT4D8odEtpOEZX5GImbBhIvwmx1hwaAFkFwc8 L4PA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Rn/GWbCehAJ+GBDtTEnmHyxU7fKIylPW3sz5YfB6oF4=; b=L9vTp7Ma90sK7OPiEYGRZZi3fUFvRNrIWEYX7qdC6KgEpBWQgheZ9hywacAdfEXBJ7 9PSs5CopWPCrpDNtO7T2euXbgB8d53Vlq1KuP8KYF3YB8+oH5TKczye2MDjU+P8f2ZRu LQLzJ9mfiIG4HpFicPlswmHTHogap5MjHioOi5vzCIvzlQyfAEe3iTPUyr+dCL/mtNx1 6kAuwiQ/Cd6hX7szVGrsCE2FqsnkJgGDCSXl7M5WDu52Zti5m58q+E7h/LJs4tP/Et+F pxg2BFMnmmJucyZVGILS6fl4VeEt+IY4FgP74CjHHYHL88G7xZ0xv1UDnPxeLWHA/Zov xY9g== X-Gm-Message-State: AOAM533E80AaM/HM3e4KkpiPoMNMPgNCjxmxX9FXDuwrlnlLLKW0JOUT gBiTs+3NWIFadsLtn74tdbMTqigPCWsKxVTmVE50Ow== X-Received: by 2002:a63:f20:: with SMTP id e32mr12949674pgl.130.1605534658700; Mon, 16 Nov 2020 05:50:58 -0800 (PST) MIME-Version: 1.0 References: <9d4156e6-ec4f-a742-a44e-f38bf7fa9ba9@arm.com> In-Reply-To: <9d4156e6-ec4f-a742-a44e-f38bf7fa9ba9@arm.com> From: Andrey Konovalov Date: Mon, 16 Nov 2020 14:50:47 +0100 Message-ID: Subject: Re: [PATCH RFC v2 04/21] kasan: unpoison stack only with CONFIG_KASAN_STACK To: Vincenzo Frascino , Dmitry Vyukov , Marco Elver , Catalin Marinas Cc: Will Deacon , Alexander Potapenko , Evgenii Stepanov , Kostya Serebryany , Peter Collingbourne , Serban Constantinescu , Andrey Ryabinin , Elena Petrova , Branislav Rankov , Kevin Brodsky , Andrew Morton , kasan-dev , Linux ARM , Linux-MM , LKML Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Nov 16, 2020 at 1:42 PM Vincenzo Frascino wrote: > > >>>> > >>>> Not sure why we did this instead of the following, but okay. > >>>> > >>>> config KASAN_STACK > >>>> - int > >>>> - default 1 if KASAN_STACK_ENABLE || CC_IS_GCC > >>>> - default 0 > >>>> + bool > >>>> + default y if KASAN_STACK_ENABLE || CC_IS_GCC > >>>> + default n > >>> > >>> I wondered the same, but then looking at scripts/Makefile.kasan I > >>> think it's because we directly pass it to the compiler: > >>> ... > >>> $(call cc-param,asan-stack=$(CONFIG_KASAN_STACK)) \ > >>> ... > >> > >> Try this instead: > >> > >> $(call cc-param,asan-stack=$(if $(CONFIG_KASAN_STACK),1,0)) \ > > > > > > We could have just 1 config instead of 2 as well. > > For gcc we could do no prompt and default value y, and for clang -- > > prompt and default value n. I think it should do what we need. > > > > I agree with Catalin's proposal since it should simplify things. > > Nit: 'default n' is the default hence I do not think it should be required > explicitly. Fixing this sounds like a good idea, but perhaps not as a part of this series, to not overinflate it even further. I've filed a bug for this: https://bugzilla.kernel.org/show_bug.cgi?id=210221