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 ports/14595] power: memset is broken on powerpc 405 Date: Fri, 13 Jun 2014 13:57:00 -0000 [thread overview] Message-ID: <bug-14595-131-0ab1xw09PW@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-14595-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=14595 Florian Weimer <fweimer at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |security? --- Comment #4 from Florian Weimer <fweimer at redhat dot com> --- Jason, does the system kind-of-sort-of work prior to applying the fix, or does it crash immediately? I wonder if we should treat this as an (architecture-specific) security issue. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2014-06-13 13:57 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-09-19 20:03 [Bug ports/14595] New: " jgunthorpe at gmail dot com 2012-09-19 20:20 ` [Bug ports/14595] " carlos_odonell at mentor dot com 2012-09-25 16:23 ` rsa at us dot ibm.com 2012-09-25 16:25 ` rsa at us dot ibm.com 2012-11-29 15:47 ` [Bug ports/14595] power: " carlos_odonell at mentor dot com 2012-11-29 15:51 ` rsa at us dot ibm.com 2014-06-13 13:57 ` fweimer at redhat dot com [this message] 2014-06-13 14:00 ` fweimer at redhat dot com 2014-06-13 15:36 ` jgunthorpe at gmail dot com 2014-06-13 15:44 ` fweimer at redhat dot com 2014-06-13 15:44 ` 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-14595-131-0ab1xw09PW@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).