[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <39df93e5-72a8-172f-866d-18d876a38d09@linux.intel.com>
Date: Wed, 5 Apr 2017 15:45:36 -0700
From: Dave Hansen <dave.hansen@...ux.intel.com>
To: Joerg Roedel <joro@...tes.org>
Cc: Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>, x86@...nel.org,
Dmitry Safonov <0x7f454c46@...il.com>,
Joerg Roedel <jroedel@...e.de>, linux-kernel@...r.kernel.org,
Borislav Petkov <bp@...e.de>
Subject: Re: [PATCH] x86/signals: Fix lower/upper bound reporting in compat
siginfo
On 04/04/2017 02:53 PM, Joerg Roedel wrote:
> On Tue, Apr 04, 2017 at 09:56:45AM -0700, Dave Hansen wrote:
>> On 04/04/2017 09:15 AM, Joerg Roedel wrote:
>>> Put the right values from the original siginfo into the
>>> userspace compat-siginfo.
>>>
>>> This fixes the 32-bit mpx tabletest on a 64-bit kernel.
>>
>> Ugh, thanks for finding that.
>
> Yeah, I was also looking at the vaddrexhaust test, but is that supposed
> to work? It does pretty weird things at least, on 64 bit the function
> effectivly does nothing because nr_to_fill evaluates to 0 there, and on
> 32 bit it gets a (probably #BF) exception which is not caught, so that
> the test fails.
>
> I am a bit confused, but maybe I just didn't stare long enough at it :-)
> Hope you can sched some light on it.
That code can probably just get removed from the tests. I haven't run
it in a while and it's probably not worth refreshing.
Powered by blists - more mailing lists