diff options
author | Andi Kleen <andi@firstfloor.org> | 2009-09-16 11:50:17 +0200 |
---|---|---|
committer | Andi Kleen <ak@linux.intel.com> | 2009-09-16 11:50:17 +0200 |
commit | f590f333fb15444d2971f979d434ecad56c09698 (patch) | |
tree | c314ba6a451a84e4232699a5794cd91ffa71e7d8 /fs/nfs/file.c | |
parent | aa261f549d7652258331ebb12795f3bc4395d213 (diff) | |
download | op-kernel-dev-f590f333fb15444d2971f979d434ecad56c09698.zip op-kernel-dev-f590f333fb15444d2971f979d434ecad56c09698.tar.gz |
HWPOISON: Enable error_remove_page for NFS
Enable hardware memory error handling for NFS
Truncation of data pages at runtime should be safe in NFS,
even when it doesn't support migration so far.
Trond tells me migration is also queued up for 2.6.32.
Acked-by: Trond.Myklebust@netapp.com
Signed-off-by: Andi Kleen <ak@linux.intel.com>
Diffstat (limited to 'fs/nfs/file.c')
-rw-r--r-- | fs/nfs/file.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/fs/nfs/file.c b/fs/nfs/file.c index 5021b75..86d6b4d 100644 --- a/fs/nfs/file.c +++ b/fs/nfs/file.c @@ -525,6 +525,7 @@ const struct address_space_operations nfs_file_aops = { .direct_IO = nfs_direct_IO, .migratepage = nfs_migrate_page, .launder_page = nfs_launder_page, + .error_remove_page = generic_error_remove_page, }; /* |