RE: mmap() of /dev/kmem issue

Luck, Tony
2004-05-05T15:08:21Z

>That's understandable. But there are cases where
>kernel values just need to be read timely. As things
>are right now you can still corrupt the kernel but
>are unable to do anything useful because of attribute
>aliasing to that range. Perhaps a rejection of mapping
>such regions for writes should be imposed, but I'm
>not sure how mapping it as uncachable helps? To
>me this behaviour seems buggy.

Mapping kernel memory as uncacheable into a user process
seems like a recipe for disaster (well at least for an
MCA when the processor catches you using mixed attributes).

-Tony