You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Eric W. Biederman 7f78e03513 fs: Limit sys_mount to only request filesystem modules. ... Modify the request_module to prefix the file system type with "fs-" and add aliases to all of the filesystems that can be built as modules to match. A common practice is to build all of the kernel code and leave code that is not commonly needed as modules, with the result that many users are exposed to any bug anywhere in the kernel. Looking for filesystems with a fs- prefix limits the pool of possible modules that can be loaded by mount to just filesystems trivially making things safer with no real cost. Using aliases means user space can control the policy of which filesystem modules are auto-loaded by editing /etc/modprobe.d/*.conf with blacklist and alias directives. Allowing simple, safe, well understood work-arounds to known problematic software. This also addresses a rare but unfortunate problem where the filesystem name is not the same as it's module name and module auto-loading would not work. While writing this patch I saw a handful of such cases. The most significant being autofs that lives in the module autofs4. This is relevant to user namespaces because we can reach the request module in get_fs_type() without having any special permissions, and people get uncomfortable when a user specified string (in this case the filesystem type) goes all of the way to request_module. After having looked at this issue I don't think there is any particular reason to perform any filtering or permission checks beyond making it clear in the module request that we want a filesystem module. The common pattern in the kernel is to call request_module() without regards to the users permissions. In general all a filesystem module does once loaded is call register_filesystem() and go to sleep. Which means there is not much attack surface exposed by loading a filesytem module unless the filesystem is mounted. In a user namespace filesystems are not mounted unless .fs_flags = FS_USERNS_MOUNT, which most filesystems do not set today. Acked-by: Serge Hallyn <serge.hallyn@canonical.com> Acked-by: Kees Cook <keescook@chromium.org> Reported-by: Kees Cook <keescook@google.com> Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>		12 years ago
..
Kconfig	fs/logfs: remove depends on CONFIG_EXPERIMENTAL	12 years ago
Makefile	…
compr.c	zlib: slim down zlib_deflate() workspace when possible	14 years ago
dev_bdev.c	logfs: query block device for number of pages to send with bio	13 years ago
dev_mtd.c	mtd: fix merge conflict resolution breakage	13 years ago
dir.c	new helper: file_inode(file)	12 years ago
file.c	new helper: file_inode(file)	12 years ago
gc.c	logfs: Prevent memory corruption	13 years ago
inode.c	Fix misspellings of "whether" in comments.	12 years ago
journal.c	logfs: create a pagecache page if it is not present	13 years ago
logfs.h	Pull request from git://github.com/prasad-joshi/logfs_upstream.git	13 years ago
logfs_abi.h	…
readwrite.c	logfs: drop vmtruncate	12 years ago
segment.c	logfs: destroy the reserved inodes while unmounting	13 years ago
super.c	fs: Limit sys_mount to only request filesystem modules.	12 years ago