Re: msync() bug

Hugh Dickins (hugh@veritas.com)
Mon, 9 Jul 2001 18:37:18 +0100 (BST)


On Mon, 9 Jul 2001, Andrea Arcangeli wrote:
> On Tue, Jul 10, 2001 at 12:43:12AM +1000, Andrew Morton wrote:
> >
> > Question: What happens if a program mmap's a part of /dev/mem
> > which passes all of these tests? Couldn't it then pick some
>
> that cannot happen, remap_pte_range only maps invalid pages or reserved
> pages.
>
> > arbitrary member of mem_map[] which may or may not have
> > a non-zero ->mapping?

Anyone know why mmap() of /dev/mem behaves in this way - solves the
problem Andrew raises, but surely that could be solved in a better way?
Seems strange that mmap() cannot give you what read() and write() can.

Hugh

-
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/