Quoting David Safford (safford@xxxxxxxxxxxxxx):
> On Wed, 2011-06-29 at 21:57 -0400, Kyle Moffett wrote:
> > There have been numerous cases in the past where a corrupt or invalid
> > filesystem causes kernel panics or even exploitable overflows or memory
> > corruption; see the history of the "fsfuzzer" tool for more information.
>
> Seems to me code bugs in the kernel should be fixed, given the universal
> practice of automounting of removable media, and loopback mounting
> images, regardless of EVM.
Hi David,
yeah, this would also be nice for making people feel cozier about
supporting unprivileged fs mounts in general. I wonder if a real
project around the idea of strengthening the robustness of the fs
code, starting with the superblock parsing for a few of the most
comment filesystems, could take off. A combination of
. code auditing and test (i.e. fsfuzzer)
. moving parts of the code to unprivileged userspace
. marking audited filesystems as unprivileged-mountable, in the
way Miklos' patchset a few years ago did
. so that those who want to can refuse auto-mount of any not
audited filesystems.
-serge
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
