On Mon, Jun 27, 2016 at 10:28 AM, Linus Torvalds
wrote:
> On Mon, Jun 27, 2016 at 8:54 AM, Andy Lutomirski wrote:
>>
>> How about:
>>
>> tsk_stack = (unsigned long)task_stack_page(tsk);
>> if (regs->rsp <= tsk_stack + 7*8 && regs->rsp >
On Mon, Jun 27, 2016 at 10:28 AM, Linus Torvalds
wrote:
> On Mon, Jun 27, 2016 at 8:54 AM, Andy Lutomirski wrote:
>>
>> How about:
>>
>> tsk_stack = (unsigned long)task_stack_page(tsk);
>> if (regs->rsp <= tsk_stack + 7*8 && regs->rsp > tsk_stack - PAGE_SIZE) {
>
> I'm not at all
On Mon, Jun 27, 2016 at 8:54 AM, Andy Lutomirski wrote:
>
> How about:
>
> tsk_stack = (unsigned long)task_stack_page(tsk);
> if (regs->rsp <= tsk_stack + 7*8 && regs->rsp > tsk_stack - PAGE_SIZE) {
I'm not at all convinced that regs->rsp will be all that reliable
On Mon, Jun 27, 2016 at 8:54 AM, Andy Lutomirski wrote:
>
> How about:
>
> tsk_stack = (unsigned long)task_stack_page(tsk);
> if (regs->rsp <= tsk_stack + 7*8 && regs->rsp > tsk_stack - PAGE_SIZE) {
I'm not at all convinced that regs->rsp will be all that reliable
under a double-fault
On Mon, Jun 27, 2016 at 1:09 PM, Brian Gerst wrote:
> On Mon, Jun 27, 2016 at 12:35 PM, Andy Lutomirski wrote:
>> On Mon, Jun 27, 2016 at 9:17 AM, Brian Gerst wrote:
>>> On Mon, Jun 27, 2016 at 11:54 AM, Andy Lutomirski
On Mon, Jun 27, 2016 at 1:09 PM, Brian Gerst wrote:
> On Mon, Jun 27, 2016 at 12:35 PM, Andy Lutomirski wrote:
>> On Mon, Jun 27, 2016 at 9:17 AM, Brian Gerst wrote:
>>> On Mon, Jun 27, 2016 at 11:54 AM, Andy Lutomirski
>>> wrote:
On Mon, Jun 27, 2016 at 8:22 AM, Andy Lutomirski
On Mon, Jun 27, 2016 at 12:35 PM, Andy Lutomirski wrote:
> On Mon, Jun 27, 2016 at 9:17 AM, Brian Gerst wrote:
>> On Mon, Jun 27, 2016 at 11:54 AM, Andy Lutomirski
>> wrote:
>>> On Mon, Jun 27, 2016 at 8:22 AM, Andy Lutomirski
On Mon, Jun 27, 2016 at 12:35 PM, Andy Lutomirski wrote:
> On Mon, Jun 27, 2016 at 9:17 AM, Brian Gerst wrote:
>> On Mon, Jun 27, 2016 at 11:54 AM, Andy Lutomirski
>> wrote:
>>> On Mon, Jun 27, 2016 at 8:22 AM, Andy Lutomirski
>>> wrote:
On Mon, Jun 27, 2016 at 8:12 AM, Brian Gerst
On Mon, Jun 27, 2016 at 9:17 AM, Brian Gerst wrote:
> On Mon, Jun 27, 2016 at 11:54 AM, Andy Lutomirski wrote:
>> On Mon, Jun 27, 2016 at 8:22 AM, Andy Lutomirski wrote:
>>> On Mon, Jun 27, 2016 at 8:12 AM, Brian Gerst
On Mon, Jun 27, 2016 at 9:17 AM, Brian Gerst wrote:
> On Mon, Jun 27, 2016 at 11:54 AM, Andy Lutomirski wrote:
>> On Mon, Jun 27, 2016 at 8:22 AM, Andy Lutomirski wrote:
>>> On Mon, Jun 27, 2016 at 8:12 AM, Brian Gerst wrote:
On Mon, Jun 27, 2016 at 11:01 AM, Brian Gerst wrote:
> On
On Mon, Jun 27, 2016 at 11:54 AM, Andy Lutomirski wrote:
> On Mon, Jun 27, 2016 at 8:22 AM, Andy Lutomirski wrote:
>> On Mon, Jun 27, 2016 at 8:12 AM, Brian Gerst wrote:
>>> On Mon, Jun 27, 2016 at 11:01 AM, Brian Gerst
On Mon, Jun 27, 2016 at 11:54 AM, Andy Lutomirski wrote:
> On Mon, Jun 27, 2016 at 8:22 AM, Andy Lutomirski wrote:
>> On Mon, Jun 27, 2016 at 8:12 AM, Brian Gerst wrote:
>>> On Mon, Jun 27, 2016 at 11:01 AM, Brian Gerst wrote:
On Sun, Jun 26, 2016 at 5:55 PM, Andy Lutomirski wrote:
>
On Mon, Jun 27, 2016 at 8:22 AM, Andy Lutomirski wrote:
> On Mon, Jun 27, 2016 at 8:12 AM, Brian Gerst wrote:
>> On Mon, Jun 27, 2016 at 11:01 AM, Brian Gerst wrote:
>>> On Sun, Jun 26, 2016 at 5:55 PM, Andy Lutomirski
On Mon, Jun 27, 2016 at 8:22 AM, Andy Lutomirski wrote:
> On Mon, Jun 27, 2016 at 8:12 AM, Brian Gerst wrote:
>> On Mon, Jun 27, 2016 at 11:01 AM, Brian Gerst wrote:
>>> On Sun, Jun 26, 2016 at 5:55 PM, Andy Lutomirski wrote:
#ifdef CONFIG_X86_64
/* Runs on IST stack */
On Mon, Jun 27, 2016 at 8:12 AM, Brian Gerst wrote:
> On Mon, Jun 27, 2016 at 11:01 AM, Brian Gerst wrote:
>> On Sun, Jun 26, 2016 at 5:55 PM, Andy Lutomirski wrote:
>>> This allows x86_64 kernels to enable vmapped stacks. There are a
>>>
On Mon, Jun 27, 2016 at 8:12 AM, Brian Gerst wrote:
> On Mon, Jun 27, 2016 at 11:01 AM, Brian Gerst wrote:
>> On Sun, Jun 26, 2016 at 5:55 PM, Andy Lutomirski wrote:
>>> This allows x86_64 kernels to enable vmapped stacks. There are a
>>> couple of interesting bits.
>>>
>>> First, x86 lazily
On Mon, Jun 27, 2016 at 11:01 AM, Brian Gerst wrote:
> On Sun, Jun 26, 2016 at 5:55 PM, Andy Lutomirski wrote:
>> This allows x86_64 kernels to enable vmapped stacks. There are a
>> couple of interesting bits.
>>
>> First, x86 lazily faults in top-level
On Mon, Jun 27, 2016 at 11:01 AM, Brian Gerst wrote:
> On Sun, Jun 26, 2016 at 5:55 PM, Andy Lutomirski wrote:
>> This allows x86_64 kernels to enable vmapped stacks. There are a
>> couple of interesting bits.
>>
>> First, x86 lazily faults in top-level paging entries for the vmalloc
>> area.
On Sun, Jun 26, 2016 at 5:55 PM, Andy Lutomirski wrote:
> This allows x86_64 kernels to enable vmapped stacks. There are a
> couple of interesting bits.
>
> First, x86 lazily faults in top-level paging entries for the vmalloc
> area. This won't work if we get a page fault while
On Sun, Jun 26, 2016 at 5:55 PM, Andy Lutomirski wrote:
> This allows x86_64 kernels to enable vmapped stacks. There are a
> couple of interesting bits.
>
> First, x86 lazily faults in top-level paging entries for the vmalloc
> area. This won't work if we get a page fault while trying to access
This allows x86_64 kernels to enable vmapped stacks. There are a
couple of interesting bits.
First, x86 lazily faults in top-level paging entries for the vmalloc
area. This won't work if we get a page fault while trying to access
the stack: the CPU will promote it to a double-fault and we'll
This allows x86_64 kernels to enable vmapped stacks. There are a
couple of interesting bits.
First, x86 lazily faults in top-level paging entries for the vmalloc
area. This won't work if we get a page fault while trying to access
the stack: the CPU will promote it to a double-fault and we'll
22 matches
Mail list logo