Re: Fatal trap 1

2012-12-22 Thread Konstantin Belousov
On Sat, Dec 22, 2012 at 01:44:49PM +0200, Andriy Gapon wrote: > on 22/12/2012 13:21 Konstantin Belousov said the following: > > This is due to the vtoslab() returning NULL. Since slabref is dereferenced > > later, clang tries to be helpful as usual and converts the !(p->flags & > > PG_SLAB) case fr

Re: Fatal trap 1

2012-12-22 Thread Andriy Gapon
on 22/12/2012 13:21 Konstantin Belousov said the following: > This is due to the vtoslab() returning NULL. Since slabref is dereferenced > later, clang tries to be helpful as usual and converts the !(p->flags & > PG_SLAB) case from vtoslab() into the jump to un2 instruction if vtoslab() > result is

Re: Fatal trap 1 [Was: "Memory modified after free" - by whom?]

2012-12-22 Thread Konstantin Belousov
On Sat, Dec 22, 2012 at 01:08:10PM +0200, Andriy Gapon wrote: > on 22/12/2012 02:21 Garrett Cooper said the following: > > Fatal trap 1: privileged instruction fault while in kernel mode > > Fatal trap 1: privileged instruction fault while in kernel mode > > Unrelated to the

Fatal trap 1 [Was: "Memory modified after free" - by whom?]

2012-12-22 Thread Andriy Gapon
on 22/12/2012 02:21 Garrett Cooper said the following: > Fatal trap 1: privileged instruction fault while in kernel mode > Fatal trap 1: privileged instruction fault while in kernel mode Unrelated to the original topic - this looks very weird. I mean all the CPUs getting this unusua