diff options
| author | Andy Lutomirski <[email protected]> | 2021-01-19 09:40:55 -0800 |
|---|---|---|
| committer | Borislav Petkov <[email protected]> | 2021-01-21 20:08:53 +0100 |
| commit | 8ece53ef7f428ee3f8eab936268b1a3fe2725e6b (patch) | |
| tree | d301122cac7f7b02c221441b4824b91144b0ec80 /net/unix/unix_bpf.c | |
| parent | b86cb29287be07041b81f5611e37ae9ffabff876 (diff) | |
x86/vm86/32: Remove VM86_SCREEN_BITMAP support
The implementation was rather buggy. It unconditionally marked PTEs
read-only, even for VM_SHARED mappings. I'm not sure whether this is
actually a problem, but it certainly seems unwise. More importantly, it
released the mmap lock before flushing the TLB, which could allow a racing
CoW operation to falsely believe that the underlying memory was not
writable.
I can't find any users at all of this mechanism, so just remove it.
Signed-off-by: Andy Lutomirski <[email protected]>
Signed-off-by: Borislav Petkov <[email protected]>
Acked-by: Stas Sergeev <[email protected]>
Link: https://lkml.kernel.org/r/f3086de0babcab36f69949b5780bde851f719bc8.1611078018.git.luto@kernel.org
Diffstat (limited to 'net/unix/unix_bpf.c')
0 files changed, 0 insertions, 0 deletions