From: "agentzh at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/30454] New: The stap runtime does not call nmi_uaccess_okay() to protect data races against CR3 switching on X86
Date: Tue, 16 May 2023 21:02:36 +0000 [thread overview]
Message-ID: <bug-30454-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=30454
Bug ID: 30454
Summary: The stap runtime does not call nmi_uaccess_okay() to
protect data races against CR3 switching on X86
Product: systemtap
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: runtime
Assignee: systemtap at sourceware dot org
Reporter: agentzh at gmail dot com
Target Milestone: ---
See the upstream kernel commit 4012e77a90 for more details.
I'm already preparing a fix.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2023-05-16 21:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 21:02 agentzh at gmail dot com [this message]
2023-05-16 21:03 ` [Bug runtime/30454] " agentzh at gmail dot com
2023-05-16 21:07 ` agentzh at gmail dot com
2023-05-16 21:31 ` agentzh at gmail dot com
2023-05-16 21:56 ` agentzh at gmail dot com
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=bug-30454-6586@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).