diff options
author | Martin Schwidefsky <schwidefsky@de.ibm.com> | 2017-08-16 14:10:01 +0200 |
---|---|---|
committer | Martin Schwidefsky <schwidefsky@de.ibm.com> | 2017-09-06 09:24:42 +0200 |
commit | b3e5dc45fd1ec2aa1de6b80008f9295eb17e0659 (patch) | |
tree | 5dbf5cd01b249aabf7dd212aae89a0c881699126 /fs/notify | |
parent | 46fde9a9d204e322cf4fda391c30213633dcc17f (diff) |
s390/mm: fix local TLB flushing vs. detach of an mm address space
The local TLB flushing code keeps an additional mask in the mm.context,
the cpu_attach_mask. At the time a global flush of an address space is
done the cpu_attach_mask is copied to the mm_cpumask in order to avoid
future global flushes in case the mm is used by a single CPU only after
the flush.
Trouble is that the reset of the mm_cpumask is racy against the detach
of an mm address space by switch_mm. The current order is first the
global TLB flush and then the copy of the cpu_attach_mask to the
mm_cpumask. The order needs to be the other way around.
Cc: <stable@vger.kernel.org>
Reviewed-by: Heiko Carstens <heiko.carstens@de.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
Diffstat (limited to 'fs/notify')
0 files changed, 0 insertions, 0 deletions