On 10/02/2014 05:23 AM, Hugh Dickins wrote: > I'm glad to hear they've confirmed some vm_area_struct corruption: > any ideas on where that's coming from?
Hugh, I think that what we're seeing isn't a corruption of vm_area_struct per-se, but something weirder. I've poisoned every spot where vm_area_struct is allocated, and yet there seems to be nothing that's hitting that field before we end up using a "zeroed out" vm_area_struct. The results are the same both with and without kasan, there seems to be no corruption happening anywhere, but we somehow end up with an empty vm_area_struct. It also somewhat makes sense considering that we're seeing no slub corruption either. Either something is zeroing out *exactly* vm_area_struct, or it's not really corruption... Thanks, Sasha -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/