From: Yu-cheng Yu <yu-cheng.yu@intel.com>
To: LKML <linux-kernel@vger.kernel.org>,
x86@kernel.org, Andy Lutomirski <luto@kernel.org>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H.J. Lu" <hjl.tools@gmail.com>, Ingo Molnar <mingo@redhat.com>,
"Ravi V. Shankar" <ravi.v.shankar@intel.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Tony Luck <tony.luck@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Weijiang Yang <weijiang.yang@intel.com>
Subject: Random shadow stack pointer corruption
Date: Sat, 18 Jul 2020 10:57:27 -0700 [thread overview]
Message-ID: <c2bfe1aa390777b10d810d2b76a35b97fbd32a1c.camel@intel.com> (raw)
Hi,
My shadow stack tests start to have random shadow stack pointer corruption after
v5.7 (excluding). The symptom looks like some locking issue or the kernel is
confused about which CPU a task is on. In later tip/master, this can be
triggered by creating two tasks and each does continuous
pthread_create()/pthread_join(). If the kernel has max_cpus=1, the issue goes
away. I also checked XSAVES/XRSTORS, but this does not seem to be an issue
coming from there.
The tests I run take a long time to complete, and some commit points in bisect
do not show failures right away. However, the issue can be more easily
triggered after the point of:
d77290507ab2 x86/entry/32: Convert IRET exception to IDTENTRY_SW
Can anyone help me find places to look at?
Thanks,
Yu-cheng
next reply other threads:[~2020-07-18 17:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-18 17:57 Yu-cheng Yu [this message]
2020-07-18 18:00 ` Andy Lutomirski
2020-07-18 18:24 ` Yu-cheng Yu
2020-07-18 18:27 ` Andy Lutomirski
2020-07-18 22:41 ` Dave Hansen
2020-07-18 23:04 ` H.J. Lu
2020-07-18 23:34 ` Yu-cheng Yu
2020-07-29 0:35 ` H.J. Lu
2020-07-29 0:56 ` Andy Lutomirski
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=c2bfe1aa390777b10d810d2b76a35b97fbd32a1c.camel@intel.com \
--to=yu-cheng.yu@intel.com \
--cc=bigeasy@linutronix.de \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hjl.tools@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=ravi.v.shankar@intel.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=weijiang.yang@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
all inboxes | Powered by JetHome®