On Tue, Nov 21, 2017 at 7:59 AM, Andy Lutomirski wrote:
> On Mon, Nov 20, 2017 at 11:33 PM, Ingo Molnar wrote:
>>
>> * Andy Lutomirski wrote:
>>
>>> This sets up stack switching, including for SYSCALL. I think it's
>>> in decent shape.
>>>
>>> Known issues:
>>> - KASAN is likely to be busted.
On Mon, Nov 20, 2017 at 11:33 PM, Ingo Molnar wrote:
>
> * Andy Lutomirski wrote:
>
>> This sets up stack switching, including for SYSCALL. I think it's
>> in decent shape.
>>
>> Known issues:
>> - KASAN is likely to be busted. This could be fixed either by teaching
>>KASAN that cpu_entry_
> On Nov 21, 2017, at 2:09 AM, Dmitry Vyukov wrote:
>
>> On Mon, Nov 20, 2017 at 10:44 PM, Andy Lutomirski wrote:
>>> On Mon, Nov 20, 2017 at 9:07 AM, Andy Lutomirski wrote:
>>> This sets up stack switching, including for SYSCALL. I think it's
>>> in decent shape.
>>>
>>> Known issues:
>>>
On Mon, Nov 20, 2017 at 10:44 PM, Andy Lutomirski wrote:
> On Mon, Nov 20, 2017 at 9:07 AM, Andy Lutomirski wrote:
>> This sets up stack switching, including for SYSCALL. I think it's
>> in decent shape.
>>
>> Known issues:
>> - KASAN is likely to be busted. This could be fixed either by teach
* Andy Lutomirski wrote:
> This sets up stack switching, including for SYSCALL. I think it's
> in decent shape.
>
> Known issues:
> - KASAN is likely to be busted. This could be fixed either by teaching
>KASAN that cpu_entry_area contains valid stacks (I have no clue how
>to go about
On Mon, Nov 20, 2017 at 9:07 AM, Andy Lutomirski wrote:
> This sets up stack switching, including for SYSCALL. I think it's
> in decent shape.
>
> Known issues:
> - KASAN is likely to be busted. This could be fixed either by teaching
>KASAN that cpu_entry_area contains valid stacks (I have
On Mon, Nov 20, 2017 at 9:07 AM, Andy Lutomirski wrote:
> This sets up stack switching, including for SYSCALL. I think it's
> in decent shape.
>
> - 32-bit kernels are failing the sigreturn_32 test. But they're also
>failing without the patches, so I'm not sure this is a bug in the
>se
This sets up stack switching, including for SYSCALL. I think it's
in decent shape.
Known issues:
- KASAN is likely to be busted. This could be fixed either by teaching
KASAN that cpu_entry_area contains valid stacks (I have no clue how
to go about doing this) or by rigging up the IST entr
8 matches
Mail list logo