From: Dave Hansen <dave.hansen@intel.com>
To: Richard Biener <rguenther@suse.de>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Cc: mhocko@suse.com
Subject: Re: Kernel bug with MPX?
Date: Thu, 7 Mar 2019 12:38:15 -0800 [thread overview]
Message-ID: <ba1d2d3c-e616-611d-3cff-acf6b8aaeb66@intel.com> (raw)
In-Reply-To: <alpine.LSU.2.20.1903060944550.7898@zhemvz.fhfr.qr>
On 3/6/19 12:53 AM, Richard Biener wrote:
> When running the gcc.target/i386/mpx/memmove-1.c testcase
> from the GCC 8 branch on MPX capable hardware the testcase
> faults and the kernel log reports the following:
While I don't doubt that we have some MPX bugs around, I wasn't able to
reproduce this one with that binary. Is there anything else that would
help us track this down?
next prev parent reply other threads:[~2019-03-07 20:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 8:53 Richard Biener
2019-03-07 20:38 ` Dave Hansen [this message]
2019-03-08 7:12 ` Michal Hocko
2019-03-08 7:41 ` Michal Hocko
2019-03-13 22:00 ` Dave Hansen
2019-03-14 16:51 ` Dave Hansen
2019-03-18 11:47 ` Michal Hocko
2019-03-18 15:59 ` Dave Hansen
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=ba1d2d3c-e616-611d-3cff-acf6b8aaeb66@intel.com \
--to=dave.hansen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=rguenther@suse.de \
/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