diff options
author | Heiko Carstens <heiko.carstens@de.ibm.com> | 2013-03-04 14:14:11 +0100 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2013-03-20 12:58:53 -0700 |
commit | 2932ef21c24f5f248b869a92c1604e531750df17 (patch) | |
tree | 87a77705d6cec9c24c15efa0eecacc4662bf80e4 /fs/btrfs | |
parent | 68e0bbe8b7781877de7dc96d620a4ce6af8807f9 (diff) | |
download | kernel_samsung_smdk4412-2932ef21c24f5f248b869a92c1604e531750df17.zip kernel_samsung_smdk4412-2932ef21c24f5f248b869a92c1604e531750df17.tar.gz kernel_samsung_smdk4412-2932ef21c24f5f248b869a92c1604e531750df17.tar.bz2 |
s390/mm: fix flush_tlb_kernel_range()
commit f6a70a07079518280022286a1dceb797d12e1edf upstream.
Our flush_tlb_kernel_range() implementation calls __tlb_flush_mm() with
&init_mm as argument. __tlb_flush_mm() however will only flush tlbs
for the passed in mm if its mm_cpumask is not empty.
For the init_mm however its mm_cpumask has never any bits set. Which in
turn means that our flush_tlb_kernel_range() implementation doesn't
work at all.
This can be easily verified with a vmalloc/vfree loop which allocates
a page, writes to it and then frees the page again. A crash will follow
almost instantly.
To fix this remove the cpumask_empty() check in __tlb_flush_mm() since
there shouldn't be too many mms with a zero mm_cpumask, besides the
init_mm of course.
Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'fs/btrfs')
0 files changed, 0 insertions, 0 deletions