Received: by 2002:ac0:a679:0:0:0:0:0 with SMTP id p54csp59184imp; Wed, 20 Feb 2019 14:14:35 -0800 (PST) X-Google-Smtp-Source: AHgI3Ialw59r4uialJKUikhv0ObY0e2PZYbYwKmnHAwxvNWOWyHaWyetFyOv0nYclwZ2FJFGa8oE X-Received: by 2002:a63:5b1f:: with SMTP id p31mr30992790pgb.56.1550700875648; Wed, 20 Feb 2019 14:14:35 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550700875; cv=none; d=google.com; s=arc-20160816; b=Wg50TfPTdkOJO+9+X3bPIK8g+lxgGXC1Oe4Dkm9iX379tKcO1DT2u58dQtj2BlwSv1 e9VTrRShJreKomJZcdPnavCLEn9tkrX9u0h+YPbkw4PlZrv9Kpyn1QhjGgTWZNd/vcfx KV6I9s0FV4PteBazlNbROLAnWpsGdiEOLdOBKwKfMKRKJzC+gfsaOlUQ4cM5zRuFPrwx I/sJ1X7JqgEDbQuCn0S1O6oGOYKxgLoPyZmCXR30n4uKgl2sv0eAi0mOjPvJ+b0Eq80q f08YHkvSBHNhPOtFdgBjzWBznJb5u7/IUkQYE624juZ8wwO7G796wbdWG6unJVzL7tNw D3cw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=tPNGEIDsIfcV4FDJtYuq+z8RJ/zCOWDCU+KMUXAGPNk=; b=gTWljzhxQFBI6I0Avdim4mwlzSJNEU9jD/lNOn2ftNkf9OK1KPmKO9256X4MoXqTiR xgo4L9dmT9zdAovJVpJxUrpynbF0dO+R2/LAe0R84CsYXje1wcyZvqOyBtufz78JbHAI 5RKeAPRH9NCJmk4KcmaJUCs9Rsm5WC6fDjzcdFMMmuIX10u/FVIDPQ0B3f1CLjfUTNvk Zjxf7Gwh0wrAXedd9R/ePF0fZO9WlkJ4QHyrunPtz5/gvdySufkrVxYe9toscHHg67rT WC5ZgBuJepbcZNPXM5jzHAPKsV0PAGN6NGkJR1PZd46I2GWUK/uS6DhA8KOr4LItBzY6 idBw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=OpNHQFA1; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 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. [209.132.180.67]) by mx.google.com with ESMTP id f12si19578799pgd.68.2019.02.20.14.14.19; Wed, 20 Feb 2019 14:14:35 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=OpNHQFA1; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 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 S1727326AbfBTWM0 (ORCPT + 99 others); Wed, 20 Feb 2019 17:12:26 -0500 Received: from mail-it1-f193.google.com ([209.85.166.193]:35562 "EHLO mail-it1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727238AbfBTWMZ (ORCPT ); Wed, 20 Feb 2019 17:12:25 -0500 Received: by mail-it1-f193.google.com with SMTP id v72so19640559itc.0 for ; Wed, 20 Feb 2019 14:12:24 -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=tPNGEIDsIfcV4FDJtYuq+z8RJ/zCOWDCU+KMUXAGPNk=; b=OpNHQFA1rrT/NK7QUnAK6GeAy+1WnKngmdbetvRhA4kO8LOcYCaPVJUUK/QOY25rGg cRUf3efe59QxFTYhh8ipHLoOHXXMFmY49mxHojbFlNQWVYaTVJ5ZVmkR9VijOghfTP1s V2yRgwlYjxdqON0Ddoe5i59+UKgv7wLAdlFX1rAd0R9+mmwZCS8r/gzvpnt9lOjuLsga AtZyX2adag/1SIsW5/6QX3f8gWhUw/UvllNI9tar6XNIHuSCQck4V3Lh7l5ewbbqZZSV Ad4EU7F4K4qHSsaTCWn/0pXSHnIWbCCdNf10GFnvlphaON3sTt34XZAJNNlYtcRAolj0 i98g== 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=tPNGEIDsIfcV4FDJtYuq+z8RJ/zCOWDCU+KMUXAGPNk=; b=FpkaQXSfPZBnLTjEF4+vkJno/w4NozVVzJqmWqGs4tDIDvkJiuj68c9+GXHdoWhpn2 SEQlgM4S2PQdo/RX5cz671ysKaYPlv/AExvPl3URKCc+pV8COBL4o74jq6jslZLT/UfT xn5yq5ZuvulpntR35biV6RD8mCyVrax4DsDDavPCxqFt7R1m39Ts+lMawbREL9tAp/l6 HIbInAvXz/QZJad4HTXexSVhhk2Lw8LhxYhY3jnvywAP0jmVFv+idG5tTa0dJzy204mo Hbo16hlvhNLwgYLIOnJFCXbZR1Qi6nWO6JuVDnWUSWNdWQOkaVfkga9kiLdP2Ok45UFD q5Kw== X-Gm-Message-State: AHQUAuY2DDpVZt/JpjNbzBsu/9WHeg2vLOsn/xFmkVIHWIlQOwix5U+e j5TzmKo6zF2C8qdqH22eAVT0xgdWdqotFJt1KZgO1g== X-Received: by 2002:a02:48c6:: with SMTP id p189mr18408837jaa.89.1550700744134; Wed, 20 Feb 2019 14:12:24 -0800 (PST) MIME-Version: 1.0 References: <20190219214940.391081-1-arnd@arndb.de> <20190220184408.GG9878@sirena.org.uk> In-Reply-To: From: Kostya Serebryany Date: Wed, 20 Feb 2019 14:12:12 -0800 Message-ID: Subject: Re: [PATCH] kasan: turn off asan-stack for clang-8 and earlier To: Arnd Bergmann Cc: Nick Desaulniers , Mark Brown , Evgenii Stepanov , Andrey Ryabinin , Andrey Konovalov , Masahiro Yamada , Michal Marek , Andrew Morton , Dmitry Vyukov , Qian Cai , Alexander Potapenko , Martin Schwidefsky , Christoph Lameter , LKML , Linux Kbuild mailing list , kasan-dev Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Feb 20, 2019 at 1:40 PM Arnd Bergmann wrote: > > On Wed, Feb 20, 2019 at 10:13 PM Arnd Bergmann wrote: > > > > In the example in https://bugs.llvm.org/show_bug.cgi?id=38809#c12 > > (https://godbolt.org/z/ylsGSQ) there is no inlining, yet clang uses > > over ten times as much stack space as gcc, for reasons I still > > can't explain. My assumption right now is that the underlying bug > > causes most of the problems with excessive stack usage in > > allmodconfig kernels. > > Here is an even more minimal example: > > struct s { int i[5]; } f(void); > void g(void) { f(); f();} On this example I can see some stupidity that clang/asan is doing. Let me try fixing it and see if it helps bigger cases. Thanks for reducing the case! This is the input we get in the asan instrumentation: ; Function Attrs: noinline nounwind optnone sanitize_address uwtable define dso_local void @g() #0 { entry: %tmp = alloca %struct.s, align 4 <<<<<<<<<<<<<<<<<<<<<<< %tmp1 = alloca %struct.s, align 4 %0 = bitcast %struct.s* %tmp to i8* call void @llvm.lifetime.start.p0i8(i64 20, i8* %0) #3 call void @f(%struct.s* sret %tmp) %1 = bitcast %struct.s* %tmp to i8* <<<<<<<<<<<<<<<<<<<<< call void @llvm.lifetime.end.p0i8(i64 20, i8* %1) #3 %2 = bitcast %struct.s* %tmp1 to i8* call void @llvm.lifetime.start.p0i8(i64 20, i8* %2) #3 <<<<<<<<<<<<< call void @f(%struct.s* sret %tmp1) %3 = bitcast %struct.s* %tmp1 to i8* call void @llvm.lifetime.end.p0i8(i64 20, i8* %3) #3 ret void } the stack variables are not *really* used, but since they are "used" inside the lifetime markers they are not eliminated by asan, and so asan instruments them, after which no one can remove them any more... > > https://godbolt.org/z/d_KWkh > > It's clear that clang does /something/ here when asan-stack=1 is > set, but I fail to see what it is, or why that is necessary. > > The output of clang with asan-stack=0 is the expected > code, and basically identical to what gcc produces with or > without asan-stack. > > Arnd