diff options
author | Heiko Carstens <heiko.carstens@de.ibm.com> | 2013-03-04 14:14:11 +0100 |
---|---|---|
committer | Martin Schwidefsky <schwidefsky@de.ibm.com> | 2013-03-05 10:21:36 +0100 |
commit | f6a70a07079518280022286a1dceb797d12e1edf (patch) | |
tree | 2ed10558860b03fd0ec751e60966f60b25d761de /drivers/s390/block | |
parent | a7bb1ae749e8051434e54936dcefd37ef1cfa753 (diff) |
s390/mm: fix flush_tlb_kernel_range()
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.
Cc: stable@vger.kernel.org
Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
Diffstat (limited to 'drivers/s390/block')
0 files changed, 0 insertions, 0 deletions