Re: [PATCH] powerpc vdso updates

[Benjamin Herrenschmidt]

> get_unmapped_area() without holding the mmap semaphore seems dangerous. 
> The VDSO setup itself should be 'private' to the process, but i'm not 
> totally sure that no other kernel code could get access to this mm. For 
> example the swapout code? Am i missing something?

Well, all of this happens so early, I doubt anything will cause actual
harm, for get_unmapped_area to be a problem, something would have to
concurrently allocate a VMA (or dispose of) I think that can't happen at
this point before we even run the binary but yes, better safe than
sorry... I supose the whole patch could get in 2.6.17 even without the
arch_vma_name (that is it can be there, it wont be used though until
your patch gets in).

Ben.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/