Re: KASAN vs vmapped stacks

2016-07-13 Thread Dmitry Vyukov
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-

Re: KASAN vs vmapped stacks

2016-07-13 Thread Dmitry Vyukov
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

Re: KASAN vs vmapped stacks

2016-07-11 Thread Andrey Ryabinin
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

Re: KASAN vs vmapped stacks

2016-07-11 Thread Andrey Ryabinin
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

Re: KASAN vs vmapped stacks

2016-07-11 Thread Andy Lutomirski
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

Re: KASAN vs vmapped stacks

2016-07-11 Thread Andy Lutomirski
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

Re: KASAN vs vmapped stacks

2016-07-11 Thread Dmitry Vyukov
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 >>

Re: KASAN vs vmapped stacks

2016-07-11 Thread Dmitry Vyukov
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

Re: KASAN vs vmapped stacks

2016-07-11 Thread Andrey Ryabinin
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

Re: KASAN vs vmapped stacks

2016-07-11 Thread Andrey Ryabinin
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

Re: KASAN vs vmapped stacks

2016-07-11 Thread Dmitry Vyukov
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 >

Re: KASAN vs vmapped stacks

2016-07-11 Thread Dmitry Vyukov
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

KASAN vs vmapped stacks

2016-07-10 Thread Andy Lutomirski
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

KASAN vs vmapped stacks

2016-07-10 Thread Andy Lutomirski
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