aboutsummaryrefslogtreecommitdiffstats
path: root/kernel
diff options
context:
space:
mode:
authorJames Bottomley <james.bottomley@steeleye.com>2004-05-23 18:20:03 -0700
committerLinus Torvalds <torvalds@ppc970.osdl.org>2004-05-23 18:20:03 -0700
commitbe4284e3a038c6d4476cf841601658321fe4c764 (patch)
treef04628bb5c4346f453ab8c786446b64ed2e3c917 /kernel
parentdcde1f6f9ce968fe453ea5c2da81408b17a6f551 (diff)
downloadhistory-be4284e3a038c6d4476cf841601658321fe4c764.tar.gz
[PATCH] pa-risc: kernel/fork.c broken by the new rmap
Any architecture (like pa-risc) that makes use of the helper function flush_dcache_mmap_lock() won't compile with the new rmap due to use of the wrong "mapping". Trivial fix.
Diffstat (limited to 'kernel')
-rw-r--r--kernel/fork.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/kernel/fork.c b/kernel/fork.c
index 42243aab170128..6dbdeec386dece 100644
--- a/kernel/fork.c
+++ b/kernel/fork.c
@@ -333,9 +333,9 @@ static inline int dup_mmap(struct mm_struct * mm, struct mm_struct * oldmm)
/* insert tmp into the share list, just after mpnt */
spin_lock(&file->f_mapping->i_mmap_lock);
- flush_dcache_mmap_lock(mapping);
+ flush_dcache_mmap_lock(file->f_mapping);
vma_prio_tree_add(tmp, mpnt);
- flush_dcache_mmap_unlock(mapping);
+ flush_dcache_mmap_unlock(file->f_mapping);
spin_unlock(&file->f_mapping->i_mmap_lock);
}