From: Peter Zijlstra <peterz@infradead.org>
To: Yujie Liu <yujie.liu@intel.com>
Cc: Andrey Ryabinin <ryabinin.a.a@gmail.com>,
oe-lkp@lists.linux.dev, lkp@intel.com,
Dave Hansen <dave.hansen@linux.intel.com>,
Seth Jenkins <sethjenkins@google.com>,
Kees Cook <keescook@chromium.org>,
linux-kernel@vger.kernel.org, x86@kernel.org,
Alexander Potapenko <glider@google.com>,
Andrey Konovalov <andreyknvl@gmail.com>,
Dmitry Vyukov <dvyukov@google.com>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
kasan-dev@googlegroups.com, "Yin,
Fengwei" <fengwei.yin@intel.com>
Subject: Re: [tip:x86/mm] [x86/mm] 1248fb6a82: Kernel_panic-not_syncing:kasan_populate_pmd:Failed_to_allocate_page
Date: Thu, 27 Oct 2022 12:13:23 +0200 [thread overview]
Message-ID: <Y1pZwwuRfYmh8A4L@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <Y1pXJheAg+sMj7eG@yujie-X299>
On Thu, Oct 27, 2022 at 06:02:14PM +0800, Yujie Liu wrote:
> Thanks for posting the fix. The issue is resolved after applying the fix.
>
> Tested-by: Yujie Liu <yujie.liu@intel.com>
Excellent; I'll talk to Dave if we want to ammend the original commit or
stuff this on top but we'll get it sorted.
Thanks!
next prev parent reply other threads:[~2022-10-27 10:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 4:54 kernel test robot
2022-10-25 10:33 ` Peter Zijlstra
2022-10-25 14:14 ` Yin, Fengwei
2022-10-25 15:39 ` Andrey Ryabinin
2022-10-27 10:02 ` Yujie Liu
2022-10-27 10:13 ` Peter Zijlstra [this message]
2022-10-27 15:12 ` Dave Hansen
2022-10-27 21:31 ` [PATCH] x86/kasan: map shadow for percpu pages on demand Andrey Ryabinin
2022-10-28 2:51 ` Yin, Fengwei
2022-10-28 14:20 ` Andrey Ryabinin
2022-10-31 0:15 ` Yin, Fengwei
2022-10-27 21:35 ` [tip:x86/mm] [x86/mm] 1248fb6a82: Kernel_panic-not_syncing:kasan_populate_pmd:Failed_to_allocate_page Andrey Ryabinin
2022-10-28 6:43 ` [tip: x86/mm] x86/kasan: Map shadow for percpu pages on demand tip-bot2 for Andrey Ryabinin
2022-12-17 18:55 ` tip-bot2 for 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=Y1pZwwuRfYmh8A4L@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=andreyknvl@gmail.com \
--cc=dave.hansen@linux.intel.com \
--cc=dvyukov@google.com \
--cc=fengwei.yin@intel.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=ryabinin.a.a@gmail.com \
--cc=sethjenkins@google.com \
--cc=vincenzo.frascino@arm.com \
--cc=x86@kernel.org \
--cc=yujie.liu@intel.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®