Re: CONFIG_UBSAN_ALIGNMENT breaks x86-64 kernel with lockdep enabled

2016-02-02 Thread Andrew Morton
On Tue, 2 Feb 2016 19:18:31 +0300 Andrey Ryabinin wrote: > > > On 02/02/2016 01:21 AM, Andrew Morton wrote: > > On Mon, 1 Feb 2016 18:10:38 +0300 Andrey Ryabinin > > wrote: > > > >> On 01/30/2016 03:36 AM, Mike Krinkin wrote: > >>> Hi, > >>> > >>> option CONFIG_UBSAN_ALIGNMENT breaks x86-64

Re: CONFIG_UBSAN_ALIGNMENT breaks x86-64 kernel with lockdep enabled

2016-02-02 Thread Andrey Ryabinin
On 02/02/2016 01:21 AM, Andrew Morton wrote: > On Mon, 1 Feb 2016 18:10:38 +0300 Andrey Ryabinin > wrote: > >> On 01/30/2016 03:36 AM, Mike Krinkin wrote: >>> Hi, >>> >>> option CONFIG_UBSAN_ALIGNMENT breaks x86-64 kernel with lockdep enabled, >>> i. e kernel with CONFIG_UBSAN_ALIGNMENT fails

Re: CONFIG_UBSAN_ALIGNMENT breaks x86-64 kernel with lockdep enabled

2016-02-01 Thread Andrew Morton
On Mon, 1 Feb 2016 18:10:38 +0300 Andrey Ryabinin wrote: > On 01/30/2016 03:36 AM, Mike Krinkin wrote: > > Hi, > > > > option CONFIG_UBSAN_ALIGNMENT breaks x86-64 kernel with lockdep enabled, > > i. e kernel with CONFIG_UBSAN_ALIGNMENT fails to load without even any > > error message. > > > >

Re: CONFIG_UBSAN_ALIGNMENT breaks x86-64 kernel with lockdep enabled

2016-02-01 Thread Andrey Ryabinin
On 01/30/2016 03:36 AM, Mike Krinkin wrote: > Hi, > > option CONFIG_UBSAN_ALIGNMENT breaks x86-64 kernel with lockdep enabled, > i. e kernel with CONFIG_UBSAN_ALIGNMENT fails to load without even any > error message. > > The problem is that ubsan callbacks use spinlocks and might be called > befo