From: Kostya Serebryany <kcc@google.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
Mark Brown <broonie@kernel.org>,
Evgenii Stepanov <eugenis@google.com>,
Andrey Ryabinin <aryabinin@virtuozzo.com>,
Andrey Konovalov <andreyknvl@google.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Michal Marek <michal.lkml@markovi.net>,
Andrew Morton <akpm@linux-foundation.org>,
Dmitry Vyukov <dvyukov@google.com>, Qian Cai <cai@lca.pw>,
Alexander Potapenko <glider@google.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Christoph Lameter <cl@linux.com>,
LKML <linux-kernel@vger.kernel.org>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
kasan-dev <kasan-dev@googlegroups.com>
Subject: Re: [PATCH] kasan: turn off asan-stack for clang-8 and earlier
Date: Wed, 20 Feb 2019 14:12:12 -0800 [thread overview]
Message-ID: <CAN=P9pi1J8fORxyp9H4WiEWWDANj0EmFOVGttDMPthUavToHBQ@mail.gmail.com> (raw)
In-Reply-To: <CAK8P3a0z7Y-uLgc8pWrdt712ic4R2nLbceg_zTCAC=ctG9LK9Q@mail.gmail.com>
On Wed, Feb 20, 2019 at 1:40 PM Arnd Bergmann <arnd@arndb.de> wrote:
>
> On Wed, Feb 20, 2019 at 10:13 PM Arnd Bergmann <arnd@arndb.de> 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
next prev parent reply other threads:[~2019-02-20 22:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 21:49 Arnd Bergmann
2019-02-19 22:17 ` Qian Cai
2019-02-19 22:43 ` Nick Desaulniers
2019-02-20 0:33 ` Kostya Serebryany
2019-02-20 1:25 ` Qian Cai
2019-02-20 6:44 ` Dmitry Vyukov
2019-02-20 9:19 ` Arnd Bergmann
2019-02-20 14:44 ` Andrey Konovalov
2019-02-20 14:51 ` Arnd Bergmann
2019-02-20 17:00 ` Andrey Ryabinin
2019-02-20 17:35 ` Arnd Bergmann
2019-02-20 18:07 ` Nick Desaulniers
2019-02-20 18:44 ` Mark Brown
2019-02-20 20:02 ` Nick Desaulniers
2019-02-20 21:13 ` Arnd Bergmann
2019-02-20 21:40 ` Arnd Bergmann
2019-02-20 22:12 ` Kostya Serebryany [this message]
2019-02-20 23:46 ` Kostya Serebryany
2019-02-21 17:19 ` Arnd Bergmann
2019-02-21 10:06 ` Andrey Ryabinin
2019-02-21 15:19 ` Arnd Bergmann
2019-02-21 16:14 ` Andrey Ryabinin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAN=P9pi1J8fORxyp9H4WiEWWDANj0EmFOVGttDMPthUavToHBQ@mail.gmail.com' \
--to=kcc@google.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@google.com \
--cc=arnd@arndb.de \
--cc=aryabinin@virtuozzo.com \
--cc=broonie@kernel.org \
--cc=cai@lca.pw \
--cc=cl@linux.com \
--cc=dvyukov@google.com \
--cc=eugenis@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=ndesaulniers@google.com \
--cc=schwidefsky@de.ibm.com \
--cc=yamada.masahiro@socionext.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®