Messages in this thread | | | Date | Fri, 2 Jul 2004 10:36:10 -0400 | Subject | Re: A question about PROT_NONE on ARM and ARM26 | From | Scott Wood <> |
| |
On Fri, Jul 02, 2004 at 12:53:54AM +0100, Jamie Lokier wrote: > The ARM uaccess code was written before CONFIG_PREEMPT was added, and > this couldn't happen then. It could panic a kernel now. I wonder why > it hasn't been noticed. Maybe nobody turns on CONFIG_PREEMPT on ARM?
Given that such behavior implies some raciness in userspace, you'd probably need either malicious or buggy user code to trigger it, and in the latter case, you're limited to apps using threads. Thus, it's probably not that surprising that it hasn't been seen.
It could also happen in other rare cases, such as if the page gets swapped out, and you get an I/O error swapping it back in, or if forced filesystem unmounting were implemented.
-Scott - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |