From: Jeremy Fitzhardinge Date: Wed, 13 Dec 2006 08:34:49 +0000 (-0800) Subject: [PATCH] Use activate_mm() in fs/aio.c:use_mm() X-Git-Tag: v2.6.20-rc1~84 X-Git-Url: https://git.karo-electronics.de/?a=commitdiff_plain;h=90aef12e6dd609e1ad7fb70044eedc78ca55ee5e;p=karo-tx-linux.git [PATCH] Use activate_mm() in fs/aio.c:use_mm() activate_mm() is not the right thing to be using in use_mm(). It should be switch_mm(). On normal x86, they're synonymous, but for the Xen patches I'm adding a hook which assumes that activate_mm is only used the first time a new mm is used after creation (I have another hook for dealing with dup_mm). I think this use of activate_mm() is the only place where it could be used a second time on an mm. >From a quick look at the other architectures I think this is OK (most simply implement one in terms of the other), but some are doing some subtly different stuff between the two. Acked-by: David Miller Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds --- diff --git a/fs/aio.c b/fs/aio.c index d3a6ec2c9627..5f577a63bdf0 100644 --- a/fs/aio.c +++ b/fs/aio.c @@ -586,7 +586,7 @@ static void use_mm(struct mm_struct *mm) * Note that on UML this *requires* PF_BORROWED_MM to be set, otherwise * it won't work. Update it accordingly if you change it here */ - activate_mm(active_mm, mm); + switch_mm(active_mm, mm, tsk); task_unlock(tsk); mmdrop(active_mm);