Messages in this thread Patch in this message |  | | | Date | Fri, 05 Jan 2007 18:28:19 -0800 | | From | Chris Wright <> | | Subject | [patch 26/50] ramfs breaks without CONFIG_BLOCK |
| |
-stable review patch. If anyone has any objections, please let us know. ------------------ From: Dimitri Gorokhovik <dimitri.gorokhovik@free.fr>
ramfs doesn't provide the .set_dirty_page a_op, and when the BLOCK layer is not configured in, 'set_page_dirty' makes a call via a NULL pointer.
Signed-off-by: Dimitri Gorokhovik <dimitri.gorokhovik@free.fr> Cc: <stable@kernel.org> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Chris Wright <chrisw@sous-sol.org> --- fs/ramfs/file-mmu.c | 4 +++- fs/ramfs/file-nommu.c | 4 +++- 2 files changed, 6 insertions(+), 2 deletions(-) --- linux-2.6.19.1.orig/fs/ramfs/file-mmu.c +++ linux-2.6.19.1/fs/ramfs/file-mmu.c @@ -25,11 +25,13 @@ */ #include <linux/fs.h> +#include <linux/mm.h> const struct address_space_operations ramfs_aops = { .readpage = simple_readpage, .prepare_write = simple_prepare_write, - .commit_write = simple_commit_write + .commit_write = simple_commit_write, + .set_page_dirty = __set_page_dirty_nobuffers, }; const struct file_operations ramfs_file_operations = { --- linux-2.6.19.1.orig/fs/ramfs/file-nommu.c +++ linux-2.6.19.1/fs/ramfs/file-nommu.c @@ -11,6 +11,7 @@ #include <linux/module.h> #include <linux/fs.h> +#include <linux/mm.h> #include <linux/pagemap.h> #include <linux/highmem.h> #include <linux/init.h> @@ -30,7 +31,8 @@ static int ramfs_nommu_setattr(struct de const struct address_space_operations ramfs_aops = { .readpage = simple_readpage, .prepare_write = simple_prepare_write, - .commit_write = simple_commit_write + .commit_write = simple_commit_write, + .set_page_dirty = __set_page_dirty_nobuffers, }; const struct file_operations ramfs_file_operations = { -- - 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/
|  |