From: Dave Hansen <dave.hansen@intel.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: Richard Biener <rguenther@suse.de>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Andrew Morton <akpm@linux-foundation.org>,
the arch/x86 maintainers <x86@kernel.org>
Subject: Re: Kernel bug with MPX?
Date: Mon, 18 Mar 2019 08:59:06 -0700 [thread overview]
Message-ID: <3e53f808-f675-0c7f-1bb2-d429f35e75a5@intel.com> (raw)
In-Reply-To: <20190318114703.GE8924@dhcp22.suse.cz>
On 3/18/19 4:47 AM, Michal Hocko wrote:
>> This is the most minimal and least invasive patch needed to
>> start removing MPX.
> Is this something we _want_ to push to stable trees?
For stable trees, probably not. It might cause a kernel update to just
break existing apps.
prev parent reply other threads:[~2019-03-18 15:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 8:53 Kernel bug with MPX? Richard Biener
2019-03-07 20:38 ` Dave Hansen
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 [this message]
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=3e53f808-f675-0c7f-1bb2-d429f35e75a5@intel.com \
--to=dave.hansen@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=rguenther@suse.de \
--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;
as well as URLs for NNTP newsgroup(s).