diff options
author | Hugh Dickins <hugh@veritas.com> | 2007-01-23 16:46:22 +0100 |
---|---|---|
committer | Adrian Bunk <bunk@stusta.de> | 2007-01-23 16:46:22 +0100 |
commit | faa309e7b921b2104a42d4ac0e0122f3399a3789 (patch) | |
tree | dca8e140dd19e48207f9c8baaf8b0dd53b7b52c2 /crypto | |
parent | 891ff634a279da34545787413355a2fd6f8487d4 (diff) |
read_zero_pagealigned() locking fix
Ramiro Voicu hits the BUG_ON(!pte_none(*pte)) in zeromap_pte_range: kernel
bugzilla 7645. Right: read_zero_pagealigned uses down_read of mmap_sem,
but another thread's racing read of /dev/zero, or a normal fault, can
easily set that pte again, in between zap_page_range and zeromap_page_range
getting there. It's been wrong ever since 2.4.3.
The simple fix is to use down_write instead, but that would serialize reads
of /dev/zero more than at present: perhaps some app would be badly
affected. So instead let zeromap_page_range return the error instead of
BUG_ON, and read_zero_pagealigned break to the slower clear_user loop in
that case - there's no need to optimize for it.
Use -EEXIST for when a pte is found: BUG_ON in mmap_zero (the other user of
zeromap_page_range), though it really isn't interesting there. And since
mmap_zero wants -EAGAIN for out-of-memory, the zeromaps better return that
than -ENOMEM.
Signed-off-by: Hugh Dickins <hugh@veritas.com>
Signed-off-by: Adrian Bunk <bunk@stusta.de>
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions