[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sat, 12 Apr 2014 20:00:46 -0700
From: "H. Peter Anvin" <hpa@...or.com>
To: Andy Lutomirski <luto@...capital.net>
CC: Alexander van Heukelum <heukelum@...tmail.fm>,
Brian Gerst <brgerst@...il.com>,
Ingo Molnar <mingo@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Thomas Gleixner <tglx@...utronix.de>, stable@...per.es
Subject: Re: [tip:x86/urgent] x86-64, modify_ldt: Ban 16-bit segments on 64-bit kernels
I would think any sensible application with 16-bit segments would be using sigaltstack. Does anyone know what Wine does?
On April 12, 2014 6:29:11 PM PDT, Andy Lutomirski <luto@...capital.net> wrote:
>On Sat, Apr 12, 2014 at 6:25 PM, Andy Lutomirski <luto@...capital.net>
>wrote:
>> On Sat, Apr 12, 2014 at 5:03 PM, H. Peter Anvin <hpa@...or.com>
>wrote:
>>> A signal arriving while in the user space trampoline could seriously
>>> complicate life.
>>
>> Agreed.
>
>Maybe I don't agree. Have signals ever worked sensibly when delivered
>to a task running on an unexpected stack or code segment?
>
>--Andy
--
Sent from my mobile phone. Please pardon brevity and lack of formatting.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists