On Mon, Jul 11, 2016 at 4:10 PM, Andrey Ryabinin
wrote:
>
>
> On 07/11/2016 01:29 PM, Dmitry Vyukov wrote:
>> On Mon, Jul 11, 2016 at 11:57 AM, Andrey Ryabinin
>> wrote:
>>>
>>>
>>> On 07/10/2016 03:47 PM, Andy Lutomirski wrote:
Hi all-
On Mon, Jul 11, 2016 at 4:10 PM, Andrey Ryabinin
wrote:
>
>
> On 07/11/2016 01:29 PM, Dmitry Vyukov wrote:
>> On Mon, Jul 11, 2016 at 11:57 AM, Andrey Ryabinin
>> wrote:
>>>
>>>
>>> On 07/10/2016 03:47 PM, Andy Lutomirski wrote:
Hi all-
I found two nasty issues with virtually
On 07/11/2016 01:29 PM, Dmitry Vyukov wrote:
> On Mon, Jul 11, 2016 at 11:57 AM, Andrey Ryabinin
> wrote:
>>
>>
>> On 07/10/2016 03:47 PM, Andy Lutomirski wrote:
>>> Hi all-
>>>
>>> I found two nasty issues with virtually mapped stacks if KASAN is
>>> enabled. The
On 07/11/2016 01:29 PM, Dmitry Vyukov wrote:
> On Mon, Jul 11, 2016 at 11:57 AM, Andrey Ryabinin
> wrote:
>>
>>
>> On 07/10/2016 03:47 PM, Andy Lutomirski wrote:
>>> Hi all-
>>>
>>> I found two nasty issues with virtually mapped stacks if KASAN is
>>> enabled. The first issue is a crash: the
On Mon, Jul 11, 2016 at 1:30 AM, Dmitry Vyukov wrote:
> On Sun, Jul 10, 2016 at 2:47 PM, Andy Lutomirski wrote:
>> Hi all-
>>
>> I found two nasty issues with virtually mapped stacks if KASAN is
>> enabled. The first issue is a crash: the first non-init
On Mon, Jul 11, 2016 at 1:30 AM, Dmitry Vyukov wrote:
> On Sun, Jul 10, 2016 at 2:47 PM, Andy Lutomirski wrote:
>> Hi all-
>>
>> I found two nasty issues with virtually mapped stacks if KASAN is
>> enabled. The first issue is a crash: the first non-init stack is
>> allocated and accessed before
On Mon, Jul 11, 2016 at 11:57 AM, Andrey Ryabinin
wrote:
>
>
> On 07/10/2016 03:47 PM, Andy Lutomirski wrote:
>> Hi all-
>>
>> I found two nasty issues with virtually mapped stacks if KASAN is
>> enabled. The first issue is a crash: the first non-init stack is
>>
On Mon, Jul 11, 2016 at 11:57 AM, Andrey Ryabinin
wrote:
>
>
> On 07/10/2016 03:47 PM, Andy Lutomirski wrote:
>> Hi all-
>>
>> I found two nasty issues with virtually mapped stacks if KASAN is
>> enabled. The first issue is a crash: the first non-init stack is
>> allocated and accessed before
On 07/10/2016 03:47 PM, Andy Lutomirski wrote:
> Hi all-
>
> I found two nasty issues with virtually mapped stacks if KASAN is
> enabled. The first issue is a crash: the first non-init stack is
> allocated and accessed before KASAN initializes its zero shadow
> AFAICT, which means that we
On 07/10/2016 03:47 PM, Andy Lutomirski wrote:
> Hi all-
>
> I found two nasty issues with virtually mapped stacks if KASAN is
> enabled. The first issue is a crash: the first non-init stack is
> allocated and accessed before KASAN initializes its zero shadow
> AFAICT, which means that we
On Sun, Jul 10, 2016 at 2:47 PM, Andy Lutomirski wrote:
> Hi all-
>
> I found two nasty issues with virtually mapped stacks if KASAN is
> enabled. The first issue is a crash: the first non-init stack is
> allocated and accessed before KASAN initializes its zero shadow
>
On Sun, Jul 10, 2016 at 2:47 PM, Andy Lutomirski wrote:
> Hi all-
>
> I found two nasty issues with virtually mapped stacks if KASAN is
> enabled. The first issue is a crash: the first non-init stack is
> allocated and accessed before KASAN initializes its zero shadow
> AFAICT, which means that
Hi all-
I found two nasty issues with virtually mapped stacks if KASAN is
enabled. The first issue is a crash: the first non-init stack is
allocated and accessed before KASAN initializes its zero shadow
AFAICT, which means that we switch to that stack and then blow up when
we start recursively
Hi all-
I found two nasty issues with virtually mapped stacks if KASAN is
enabled. The first issue is a crash: the first non-init stack is
allocated and accessed before KASAN initializes its zero shadow
AFAICT, which means that we switch to that stack and then blow up when
we start recursively
14 matches
Mail list logo