> >
> >The root of the problem is that copy_to_user() may cause page faults
> >on the userspace buffer, and the page fault might (in case of a
> >maliciously crafted filesystem) recurse into the filesystem itself.
>
> Would it be worthwhile to mlock the page? I know that needs root
> privs or some capability, but a static buffer could be put aside when
> fusermount is run.
And how would the kernel ensure, that the buffer supplied by userspace
is mlocked and stays mlocked during the memory copy? I don't think
that would simplify the kerel side much, and would complicate the
userspace side considerably.
Miklos
-
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/
- References:
- fuse, get_user_pages, flush_anon_page, aliasing caches and all that again
- From: Russell King <rmk+lkml@arm.linux.org.uk>
- Re: fuse, get_user_pages, flush_anon_page, aliasing caches and all that again
- From: Miklos Szeredi <miklos@szeredi.hu>
- Re: fuse, get_user_pages, flush_anon_page, aliasing caches and all that again
- From: Russell King <rmk+lkml@arm.linux.org.uk>
- Re: fuse, get_user_pages, flush_anon_page, aliasing caches and all that again
- From: Miklos Szeredi <miklos@szeredi.hu>
- Re: fuse, get_user_pages, flush_anon_page, aliasing caches and all that again
- From: Jan Engelhardt <jengelh@linux01.gwdg.de>
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]