From: Linus Torvalds <torvalds@linux-foundation.org>
To: Andrew Morton <akpm@linux-foundation.org>,
Alexander Potapenko <glider@google.com>,
Andrey Konovalov <andreyknvl@google.com>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Cc: 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: Mon, 10 Oct 2022 18:20:00 -0700 [thread overview]
Message-ID: <CAHk-=wigZoriP8ZB+V87Jf+EQV=ka6DQe_HCAQmh3Dmus2FFhw@mail.gmail.com> (raw)
In-Reply-To: <20221008132113.919b9b894426297de78ac00f@linux-foundation.org>
On Sat, Oct 8, 2022 at 1:21 PM Andrew Morton <akpm@linux-foundation.org> wrote:
>
> Alexander Potapenko (43):
> crypto: kmsan: disable accelerated configs under KMSAN
Ok, so this conflicted pretty badly with the crypto tree having
re-organized their Kconfig files.
I channelled my inner Alexander the Great, and just cut the whole
thing through by disabling all the architecture-accelerated crypto
includes when KMSAN was enabled.
But that's very different from your tree that disabled the options
individually, so some KMSAN person should probably look around at it
and decide whether some more subtle approach is called for.
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
which may just be a "need to teach objtool this is ok", but I'm not
seeing why it's now starting to happen. Maybe just code generation
changed for some reason, or maybe it's just that config options ended
up changing enough to expose this on my allmodconfig builds.
Cc'ing people who may know better.
This is just my reaction from doing the merge and test-build. There
may or may not be more commentary once I've actually tried to boot
into this thing.
Linus
next prev parent reply other threads:[~2022-10-11 1:20 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 [this message]
2022-10-11 8:24 ` Peter Zijlstra
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='CAHk-=wigZoriP8ZB+V87Jf+EQV=ka6DQe_HCAQmh3Dmus2FFhw@mail.gmail.com' \
--to=torvalds@linux-foundation.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=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).