From: Peter Zijlstra <peterz@infradead.org>
To: kernel test robot <oliver.sang@intel.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
Dave Hansen <dave.hansen@intel.com>,
linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: [tip:x86/mm] [x86/mm] 127960a055: WARNING:at_arch/x86/include/asm/kfence.h:#kfence_protect
Date: Mon, 21 Nov 2022 12:29:56 +0100 [thread overview]
Message-ID: <Y3thNAR4AV8Lp1qZ@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <202211201642.b65c9d2f-oliver.sang@intel.com>
On Sun, Nov 20, 2022 at 04:40:51PM +0800, kernel test robot wrote:
>
> hi, PeterZ,
>
> we noticed this is a fix for
> "[tip:x86/mm] [x86/mm] b389949485: WARNING:at_arch/x86/mm/pat/set_memory.c:#__change_page_attr"
> we reported before on
> https://lore.kernel.org/all/202211061748.eb591682-oliver.sang@intel.com/
> we noticed it brought below issue which is persistent in our tests. FYI
>
>
> Greeting,
>
> FYI, we noticed WARNING:at_arch/x86/include/asm/kfence.h:#kfence_protect due to commit (built with gcc-11):
>
> commit: 127960a05548ea699a95791669e8112552eb2452 ("x86/mm: Inhibit _PAGE_NX changes from cpa_process_alias()")
> https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git x86/mm
>
> in testcase: boot
>
> on test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
>
> caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
>
>
> +----------------------------------------------------------+------------+------------+
> | | 5ab815e377 | 127960a055 |
> +----------------------------------------------------------+------------+------------+
> | WARNING:at_arch/x86/include/asm/kfence.h:#kfence_protect | 0 | 15 |
> | RIP:kfence_protect | 0 | 15 |
> | WARNING:at_mm/kfence/core.c:#kfence_protect | 0 | 15 |
> +----------------------------------------------------------+------------+------------+
>
>
> If you fix the issue, kindly add following tag
> | Reported-by: kernel test robot <oliver.sang@intel.com>
> | Link: https://lore.kernel.org/oe-lkp/202211201642.b65c9d2f-oliver.sang@intel.com
>
>
> [ 1.269844][ T0] ------------[ cut here ]------------
> [ 1.270843][ T0] WARNING: CPU: 0 PID: 0 at arch/x86/include/asm/kfence.h:46 kfence_protect (arch/x86/include/asm/kfence.h:46 mm/kfence/core.c:235)
Should be fixed by:
https://lkml.kernel.org/r/41ac24c4-6c95-d946-2679-c1be2cb20536@intel.com
I think.
prev parent reply other threads:[~2022-11-21 11:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-20 8:40 [tip:x86/mm] [x86/mm] 127960a055: WARNING:at_arch/x86/include/asm/kfence.h:#kfence_protect kernel test robot
2022-11-21 11:29 ` Peter Zijlstra [this message]
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=Y3thNAR4AV8Lp1qZ@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=dave.hansen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=x86@kernel.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).