public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/25954] New: Missing content-synchronizing instructions in pkey_set on POWER Date: Fri, 08 May 2020 20:03:02 +0000 [thread overview] Message-ID: <bug-25954-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=25954 Bug ID: 25954 Summary: Missing content-synchronizing instructions in pkey_set on POWER Product: glibc Version: unspecified Status: NEW Severity: normal Priority: P2 Component: libc Assignee: unassigned at sourceware dot org Reporter: fweimer at redhat dot com CC: drepper.fsp at gmail dot com Target Milestone: --- Target: powerpc64* Flags: security- Sandipan Das reported this bug against the kernel protection key self-tests: “ The Power ISA mandates that all writes to the Authority Mask Register (AMR) must always be preceded as well as succeeded by a context-synchronizing instruction. This applies to both the privileged and unprivileged variants of the Move To AMR instruction. This [requirement] is from Table 6 of Chapter 11 in page 1134 of Power ISA 3.0B. The document can be found here: https://ibm.ent.box.com/s/1hzcwkwf8rbju5h9iyf44wm94amnlcrv ” <https://lore.kernel.org/linuxppc-dev/5f65cf37be993760de8112a88da194e3ccbb2bf8.1588959697.git.sandipan@linux.ibm.com/> We need to add these additonal instructions to the pkey_set implementation in glibc, too. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2020-05-08 20:03 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-08 20:03 fweimer at redhat dot com [this message] 2020-05-08 20:03 ` [Bug libc/25954] " fweimer at redhat dot com 2020-05-08 20:09 ` [Bug libc/25954] Missing context-synchronizing " fweimer at redhat dot com 2020-05-11 10:13 ` fweimer at redhat dot com 2020-05-11 22:05 ` tuliom at ascii dot art.br 2023-07-02 16:07 ` fweimer at redhat dot com 2023-07-02 16:08 ` fweimer at redhat 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-25954-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@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: linkBe 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).