From: Peter Zijlstra <peterz@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Alexander Potapenko <glider@google.com>,
Andrey Konovalov <andreyknvl@google.com>,
Josh Poimboeuf <jpoimboe@kernel.org>,
mm-commits@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] MM updates for 6.1-rc1
Date: Tue, 11 Oct 2022 10:24:27 +0200 [thread overview]
Message-ID: <Y0UoO2+NsJjbZtaf@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <CAHk-=wigZoriP8ZB+V87Jf+EQV=ka6DQe_HCAQmh3Dmus2FFhw@mail.gmail.com>
On Mon, Oct 10, 2022 at 06:20:00PM -0700, Linus Torvalds wrote:
> The other thing I notice from just doing a build is that I now get
>
> vmlinux.o: warning: objtool: kasan_report+0x12: call to
> stackleak_track_stack() with UACCESS enabled
So kasan_report() is already marked as being special; and it does the
mandatory user_access_save() / user_access_restore() things to fix it
up.
But it looks like kasan code itself is now getting instrumented by the
stackleak stuff and that inserts a call outside of the
user_access_save()/restore() thing, and *that* is getting flagged.
Looking at mm/kasan/Makefile it disables a lot of the instrumentation,
but perhaps not enough?
I've not yet tried to reproduce, I'm taking this is allyesconfig or
something glorious like that? LLVM-15 ?
next prev parent reply other threads:[~2022-10-11 8:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-08 20:21 [GIT PULL] MM updates for 6.1-rc1 Andrew Morton
2022-10-11 1:20 ` Linus Torvalds
2022-10-11 8:24 ` Peter Zijlstra [this message]
2022-10-11 17:08 ` Linus Torvalds
2022-10-11 18:44 ` Josh Poimboeuf
2022-10-11 18:59 ` Josh Poimboeuf
2022-10-11 19:05 ` [PATCH] kasan: disable stackleak plugin in report code Josh Poimboeuf
2022-10-11 22:00 ` Linus Torvalds
2022-10-11 9:02 ` [GIT PULL] MM updates for 6.1-rc1 Alexander Potapenko
2022-10-11 17:11 ` Linus Torvalds
2022-10-11 1:23 ` pr-tracker-bot
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=Y0UoO2+NsJjbZtaf@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@google.com \
--cc=glider@google.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mm-commits@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.