On Wed, May 14, 2014 at 2:31 PM, Andrew Morton <a...@linux-foundation.org> wrote: > On Wed, 14 May 2014 17:11:00 -0400 Sasha Levin <sasha.le...@oracle.com> wrote: > >> > In my linux-next all that code got deleted by Andy's "x86, vdso: >> > Reimplement vdso.so preparation in build-time C" anyway. What kernel >> > were you looking at? >> >> Deleted? It appears in today's -next. arch/x86/vdso/vma.c:124 . >> >> I don't see Andy's patch removing that code either. > > ah, OK, it got moved from arch/x86/vdso/vdso32-setup.c into > arch/x86/vdso/vma.c. > > Maybe you managed to take a fault against the symbol area between the > _install_special_mapping() and the remap_pfn_range() call, but mmap_sem > should prevent that. > > Or the remap_pfn_range() call never happened. Should map_vdso() be > running _install_special_mapping() at all if > image->sym_vvar_page==NULL?
I'm confused: are we talking about 3.15-rcsomething or linux-next? That code changed. Would this all make more sense if there were just a single vma in here? cc: Pavel and Cyrill, who might have to deal with this stuff in CRIU --Andy -- Andy Lutomirski AMA Capital Management, LLC -- 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/