diff options
author | Jeremy Fitzhardinge <jeremy@goop.org> | 2006-12-13 00:34:49 -0800 |
---|---|---|
committer | Linus Torvalds <torvalds@woody.osdl.org> | 2006-12-13 09:05:51 -0800 |
commit | 90aef12e6dd609e1ad7fb70044eedc78ca55ee5e (patch) | |
tree | 35ff39f80d010c548df660d3a3e53c5861741777 /drivers/pnp/pnpbios | |
parent | 74c383f1400f559562aa517d6d62f77245bddf52 (diff) | |
download | op-kernel-dev-90aef12e6dd609e1ad7fb70044eedc78ca55ee5e.zip op-kernel-dev-90aef12e6dd609e1ad7fb70044eedc78ca55ee5e.tar.gz |
[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 <davem@davemloft.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'drivers/pnp/pnpbios')
0 files changed, 0 insertions, 0 deletions