All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Dave Hansen <dave.hansen@intel.com>, Andi Kleen <andi@firstfloor.org>
Cc: mtk.manpages@gmail.com, Andrew Morton <akpm@linux-foundation.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	Qiaowei Ren <qiaowei.ren@intel.com>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86, mpx: Ensure unused arguments of prctl() MPX requests are 0
Date: Sat, 10 Jan 2015 14:49:07 +0100	[thread overview]
Message-ID: <54B12DD3.5020605@gmail.com> (raw)
In-Reply-To: <54B01F41.10001@intel.com>

On 01/09/2015 07:34 PM, Dave Hansen wrote:
> On 01/09/2015 10:25 AM, Michael Kerrisk (man-pages) wrote:
>> On 9 January 2015 at 18:25, Andi Kleen <andi@firstfloor.org> wrote:
>>> "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com> writes:
>>>> From: Michael Kerrisk <mtk.manpages@gmail.com>
>>>>
>>>> commit fe8c7f5cbf91124987106faa3bdf0c8b955c4cf7 added two new prctl()
>>>> operations, PR_MPX_ENABLE_MANAGEMENT and PR_MPX_DISABLE_MANAGEMENT.
>>>> However, no checks were included to ensure that unused arguments
>>>> are zero, as is done in many existing prctl()s and as should be
>>>> done for all new prctl()s. This patch adds the required checks.
>>>
>>> This will break the existing gcc run time, which doesn't zero these
>>> arguments.
>>
>> I'm a little lost here. Weren't these flags new in the
>> as-yet-unreleased 3.19? How does gcc run-time depends on them already?
> 
> These prctl()s have been around in some form or another for a few months
> since the patches had not yet been merged in to the kernel.  There is
> support for them in a set of (yet unmerged) gcc patches, as well as some
> tests which are only internal to Intel.
> 
> This change will, indeed, break those internal tests as well as the gcc
> patches.  As far as I know, the code is not in production anywhere and
> can be changed.  The prctl() numbers have changed while the patches were
> out of tree and it's a somewhat painful process each time it changes.
> It's not impossible, just painful.

So, sounds like thinks can be fixed (with mild inconvenience), and they
should be fixed before 3.19 is actually released.

Cheers,

Michael



-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

WARNING: multiple messages have this Message-ID (diff)
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Dave Hansen <dave.hansen@intel.com>, Andi Kleen <andi@firstfloor.org>
Cc: mtk.manpages@gmail.com, Andrew Morton <akpm@linux-foundation.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	Qiaowei Ren <qiaowei.ren@intel.com>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86, mpx: Ensure unused arguments of prctl() MPX requests are 0
Date: Sat, 10 Jan 2015 14:49:07 +0100	[thread overview]
Message-ID: <54B12DD3.5020605@gmail.com> (raw)
In-Reply-To: <54B01F41.10001@intel.com>

On 01/09/2015 07:34 PM, Dave Hansen wrote:
> On 01/09/2015 10:25 AM, Michael Kerrisk (man-pages) wrote:
>> On 9 January 2015 at 18:25, Andi Kleen <andi@firstfloor.org> wrote:
>>> "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com> writes:
>>>> From: Michael Kerrisk <mtk.manpages@gmail.com>
>>>>
>>>> commit fe8c7f5cbf91124987106faa3bdf0c8b955c4cf7 added two new prctl()
>>>> operations, PR_MPX_ENABLE_MANAGEMENT and PR_MPX_DISABLE_MANAGEMENT.
>>>> However, no checks were included to ensure that unused arguments
>>>> are zero, as is done in many existing prctl()s and as should be
>>>> done for all new prctl()s. This patch adds the required checks.
>>>
>>> This will break the existing gcc run time, which doesn't zero these
>>> arguments.
>>
>> I'm a little lost here. Weren't these flags new in the
>> as-yet-unreleased 3.19? How does gcc run-time depends on them already?
> 
> These prctl()s have been around in some form or another for a few months
> since the patches had not yet been merged in to the kernel.  There is
> support for them in a set of (yet unmerged) gcc patches, as well as some
> tests which are only internal to Intel.
> 
> This change will, indeed, break those internal tests as well as the gcc
> patches.  As far as I know, the code is not in production anywhere and
> can be changed.  The prctl() numbers have changed while the patches were
> out of tree and it's a somewhat painful process each time it changes.
> It's not impossible, just painful.

So, sounds like thinks can be fixed (with mild inconvenience), and they
should be fixed before 3.19 is actually released.

Cheers,

Michael



-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

  reply	other threads:[~2015-01-10 13:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-08 10:28 [PATCH] x86, mpx: Ensure unused arguments of prctl() MPX requests are 0 Michael Kerrisk (man-pages)
2015-01-08 10:28 ` Michael Kerrisk (man-pages)
2015-01-09 17:25 ` Andi Kleen
2015-01-09 17:25   ` Andi Kleen
2015-01-09 18:25   ` Michael Kerrisk (man-pages)
2015-01-09 18:25     ` Michael Kerrisk (man-pages)
2015-01-09 18:34     ` Dave Hansen
2015-01-09 18:34       ` Dave Hansen
2015-01-10 13:49       ` Michael Kerrisk (man-pages) [this message]
2015-01-10 13:49         ` Michael Kerrisk (man-pages)
2015-01-10 18:39         ` Andi Kleen
2015-01-10 18:39           ` Andi Kleen
2015-01-14  7:21           ` Michael Kerrisk (man-pages)
2015-01-14  7:21             ` Michael Kerrisk (man-pages)

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=54B12DD3.5020605@gmail.com \
    --to=mtk.manpages@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=dave.hansen@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=qiaowei.ren@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.