Re: Making KASAN compatible with VMAP_STACK

2018-12-17 Thread Dmitry Vyukov
On Mon, Jul 23, 2018 at 2:51 PM Dmitry Vyukov wrote: > > On Mon, Jul 23, 2018 at 2:42 PM, Mark Rutland wrote: > >> >> > Hi all- > >> >> > > >> >> > It would be really nice to make KASAN compatible with VMAP_STACK. > >> >> > Both are valuable memory debugging features, and the fact that you > >>

Re: Making KASAN compatible with VMAP_STACK

2018-07-23 Thread Dmitry Vyukov
On Mon, Jul 23, 2018 at 2:42 PM, Mark Rutland wrote: >> >> > Hi all- >> >> > >> >> > It would be really nice to make KASAN compatible with VMAP_STACK. >> >> > Both are valuable memory debugging features, and the fact that you >> >> > can't use both is disappointing. >> >> > >> >> > As far as I

Re: Making KASAN compatible with VMAP_STACK

2018-07-23 Thread Dmitry Vyukov
On Mon, Jul 23, 2018 at 2:42 PM, Mark Rutland wrote: >> >> > Hi all- >> >> > >> >> > It would be really nice to make KASAN compatible with VMAP_STACK. >> >> > Both are valuable memory debugging features, and the fact that you >> >> > can't use both is disappointing. >> >> > >> >> > As far as I

Re: Making KASAN compatible with VMAP_STACK

2018-07-23 Thread Mark Rutland
On Mon, Jul 23, 2018 at 01:55:49PM +0200, Dmitry Vyukov wrote: > On Mon, Jul 23, 2018 at 1:18 PM, Mark Rutland wrote: > > On Mon, Jul 23, 2018 at 09:40:36AM +0200, Dmitry Vyukov wrote: > >> On Sun, Jul 22, 2018 at 7:52 PM, Andy Lutomirski wrote: > >> > Hi all- > >> > > >> > It would be really

Re: Making KASAN compatible with VMAP_STACK

2018-07-23 Thread Mark Rutland
On Mon, Jul 23, 2018 at 01:55:49PM +0200, Dmitry Vyukov wrote: > On Mon, Jul 23, 2018 at 1:18 PM, Mark Rutland wrote: > > On Mon, Jul 23, 2018 at 09:40:36AM +0200, Dmitry Vyukov wrote: > >> On Sun, Jul 22, 2018 at 7:52 PM, Andy Lutomirski wrote: > >> > Hi all- > >> > > >> > It would be really

Re: Making KASAN compatible with VMAP_STACK

2018-07-23 Thread Dmitry Vyukov
On Mon, Jul 23, 2018 at 1:18 PM, Mark Rutland wrote: > On Mon, Jul 23, 2018 at 09:40:36AM +0200, Dmitry Vyukov wrote: >> On Sun, Jul 22, 2018 at 7:52 PM, Andy Lutomirski wrote: >> > Hi all- >> > >> > It would be really nice to make KASAN compatible with VMAP_STACK. >> > Both are valuable memory

Re: Making KASAN compatible with VMAP_STACK

2018-07-23 Thread Dmitry Vyukov
On Mon, Jul 23, 2018 at 1:18 PM, Mark Rutland wrote: > On Mon, Jul 23, 2018 at 09:40:36AM +0200, Dmitry Vyukov wrote: >> On Sun, Jul 22, 2018 at 7:52 PM, Andy Lutomirski wrote: >> > Hi all- >> > >> > It would be really nice to make KASAN compatible with VMAP_STACK. >> > Both are valuable memory

Re: Making KASAN compatible with VMAP_STACK

2018-07-23 Thread Mark Rutland
On Mon, Jul 23, 2018 at 09:40:36AM +0200, Dmitry Vyukov wrote: > On Sun, Jul 22, 2018 at 7:52 PM, Andy Lutomirski wrote: > > Hi all- > > > > It would be really nice to make KASAN compatible with VMAP_STACK. > > Both are valuable memory debugging features, and the fact that you > > can't use both

Re: Making KASAN compatible with VMAP_STACK

2018-07-23 Thread Mark Rutland
On Mon, Jul 23, 2018 at 09:40:36AM +0200, Dmitry Vyukov wrote: > On Sun, Jul 22, 2018 at 7:52 PM, Andy Lutomirski wrote: > > Hi all- > > > > It would be really nice to make KASAN compatible with VMAP_STACK. > > Both are valuable memory debugging features, and the fact that you > > can't use both

Re: Making KASAN compatible with VMAP_STACK

2018-07-23 Thread Dmitry Vyukov
On Sun, Jul 22, 2018 at 7:52 PM, Andy Lutomirski wrote: > Hi all- > > It would be really nice to make KASAN compatible with VMAP_STACK. > Both are valuable memory debugging features, and the fact that you > can't use both is disappointing. > > As far as I know, there are only two problems: > > 1.

Re: Making KASAN compatible with VMAP_STACK

2018-07-23 Thread Dmitry Vyukov
On Sun, Jul 22, 2018 at 7:52 PM, Andy Lutomirski wrote: > Hi all- > > It would be really nice to make KASAN compatible with VMAP_STACK. > Both are valuable memory debugging features, and the fact that you > can't use both is disappointing. > > As far as I know, there are only two problems: > > 1.