From: Uros Bizjak <ubizjak@gmail.com>
To: kernel test robot <oliver.sang@intel.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
Nadav Amit <namit@vmware.com>, Andy Lutomirski <luto@kernel.org>,
Brian Gerst <brgerst@gmail.com>,
Denys Vlasenko <dvlasenk@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Josh Poimboeuf <jpoimboe@redhat.com>,
linux-mm@kvack.org
Subject: Re: [linus:master] [x86/percpu] ca42563486: BUG:unable_to_handle_page_fault_for_address
Date: Mon, 25 Mar 2024 11:31:40 +0100 [thread overview]
Message-ID: <CAFULd4bFbhOQ+mx2=pKqLbLznR-UFZamS4HhdUYZF2qFKNcDVg@mail.gmail.com> (raw)
In-Reply-To: <202403251658.8e92a8bc-lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1623 bytes --]
On Mon, Mar 25, 2024 at 9:50 AM kernel test robot <oliver.sang@intel.com> wrote:
>
>
> hi, Uros Bizjak,
>
> we reported an early crash issue for this commit last Oct.
> https://lore.kernel.org/all/202310071301.a5113890-oliver.sang@intel.com/
>
> as you mentioned at that time
> "It is KASAN that is not compatible with named address spaces [1]."
>
> now we noticed the commit is merged into mainline, and we observed a different
> issue related with kcsan_setup_watchpoint. below detail report FYI.
>
> [1] https://lore.kernel.org/lkml/CAHk-=wi6U-O1wdPOESuCE6QO2OaPu0hEzaig0uDOU4L5CREhug@mail.gmail.com/
>
Yes, it is the same issue, but with KCSAN.
> Hello,
>
> kernel test robot noticed "BUG:unable_to_handle_page_fault_for_address" on:
>
> commit: ca4256348660cb2162668ec3d13d1f921d05374a ("x86/percpu: Use C for percpu read/write accessors")
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
>
> [test failed on linus/master b3603fcb79b1036acae10602bffc4855a4b9af80]
> [test failed on linux-next/master 226d3c72fcde130a99d760895ebdd20e78e02cb5]
>
> in testcase: boot
>
> compiler: gcc-12
> test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
We already have the candidate fix for GCC [1], the fix will be in gcc-13.3+.
[1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111736
Please find attached an emergency patch for mainline that disables
named address spaces when KCSAN is enabled. I'll post a formal patch
submission in a moment. The named AS will be re-enabled with KCSAN
with a patch via -tip tree.
Thanks,
Uros.
[-- Attachment #2: p.diff.txt --]
[-- Type: text/plain, Size: 403 bytes --]
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index 39886bab943a..4fff6ed46e90 100644
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@ -2439,6 +2439,8 @@ config USE_X86_SEG_SUPPORT
# with named address spaces - see GCC PR sanitizer/111736.
#
depends on !KASAN
+ # -fsanitize=thread (KCSAN) is also incompatible.
+ depends on !KCSAN
config CC_HAS_SLS
def_bool $(cc-option,-mharden-sls=all)
next prev parent reply other threads:[~2024-03-25 10:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 8:49 kernel test robot
2024-03-25 10:31 ` Uros Bizjak [this message]
2024-03-27 2:27 ` Oliver Sang
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='CAFULd4bFbhOQ+mx2=pKqLbLznR-UFZamS4HhdUYZF2qFKNcDVg@mail.gmail.com' \
--to=ubizjak@gmail.com \
--cc=brgerst@gmail.com \
--cc=dvlasenk@redhat.com \
--cc=hpa@zytor.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=namit@vmware.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox