Re: [Xen-devel] vmalloc_sync_all crash still happening on some machines

[Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>]

Ian Campbell writes ("Re: [Xen-devel] vmalloc_sync_all crash still happening on 
some machines"):
> More specifically it seems to be
> 6bec8b4a4c14095d0b7ce424db9d583c3decae6c from Jeremy's xen/next-2.6.32
> branch.

My script is still pulling from Jeremy's github.  I see that the tree
on git.kernel.org has many new changesets so I'll switch back to that.
I guess I naively assumed that having established two trees Jeremy
might push to both of them...

> I suspect that's a red-herring though since I bet the vmalloc fixes
> simply never got backported to this tree.

Yes, it looks like they didn't.

Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel