On Tue, 4 Oct 2011, Russell King - ARM Linux wrote: > On Tue, Oct 04, 2011 at 05:10:36PM -0400, Nicolas Pitre wrote: > > Which makes me think... with all those architectures intercepting > > ioremap calls in order to provide an equivalent static mapping address, > > they already get an unexpected domain given that static mappings are > > mostly DOMAIN_IO and not DOMAIN_KERNEL as would result from an non > > intercepted ioremap call. > > That's a necessary evil - otherwise we have to separate out the > ioremap from vmalloc. > > Incidentally, how are you dealing with the problem of a static mapping > setting up a L1 page table entry for DOMAIN_IO, and then a vmalloc > request coming in, overlapping that L1 page table? > > If this memory then gets accessed with get_user() with set_fs(get_ds()), > the kernel will oops as we don't switch DOMAIN_IO memory on set_fs(). > (I don't know if this happens in practice, but there's nothing to say > that it's illegal to do this.) I suppose that didn't happen so far. Granted, moving the ioremap optimization into core code for all machines will increase the possibility for this to happen, even if still small. With CPU_USE_DOMAINS not set, set_fs() is a no-op anyway, besides addr_limit that is. Is there a strong benefit in having static mappings being DOMAIN_IO instead of DOMAIN_KERNEL? Nicolas -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
