diff options
author | Linus Torvalds <[email protected]> | 2021-05-19 05:55:57 -1000 |
---|---|---|
committer | Linus Torvalds <[email protected]> | 2021-05-19 05:55:57 -1000 |
commit | 293837b9ac8d3021657f44c9d7a14948ec01c5d0 (patch) | |
tree | 10b6a90b0c7e2c03d8640bc9d0b550720b75ebcf /scripts/gdb/linux | |
parent | 8ac91e6c6033ebc12c5c1e4aa171b81a662bd70f (diff) |
Revert "i915: fix remap_io_sg to verify the pgprot"
This reverts commit b12d691ea5e01db42ccf3b4207e57cb3ce7cfe91.
It turns out this is not ready for primetime yet. The intentions are
good, but using remap_pfn_range() requires that there is nothing already
mapped in the area, and the i915 code seems to very much intentionally
remap the same area multiple times.
That will then just trigger the
BUG_ON(!pte_none(*pte));
in mm/memory.c: remap_pte_range().
There are also reports of mapping type inconsistencies, resulting in
warnings and in screen corruption.
Link: https://lore.kernel.org/lkml/20210519024322.GA29704@xsang-OptiPlex-9020/
Link: https://lore.kernel.org/lkml/YKUjvoaKKggAmpIR@sf/
Link: https://lore.kernel.org/lkml/[email protected]/
Reported-by: kernel test robot <[email protected]>
Reported-by: Kalle Valo <[email protected]>
Reported-by: Hans de Goede <[email protected]>
Reported-by: Sergei Trofimovich <[email protected]>
Acked-by: Christoph Hellwig <[email protected]>
Cc: Chris Wilson <[email protected]>
Cc: Daniel Vetter <[email protected]>
Cc: Jani Nikula <[email protected]>
Cc: Joonas Lahtinen <[email protected]>
Cc: Peter Zijlstra <[email protected]>
Cc: Rodrigo Vivi <[email protected]>
Cc: Andrew Morton <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'scripts/gdb/linux')
0 files changed, 0 insertions, 0 deletions