diff options
| author | Michael Kelley <[email protected]> | 2025-02-09 23:52:52 +0000 |
|---|---|---|
| committer | Wei Liu <[email protected]> | 2025-02-21 19:45:02 +0000 |
| commit | 7241c886a71797cc51efc6fadec7076fcf6435c2 (patch) | |
| tree | 48395336e30adce7faee8c8e36d2245d2664d829 /tools/testing/selftests/kvm/x86/nested_exceptions_test.c | |
| parent | x86/hyperv/vtl: Stop kernel from probing VTL0 low memory (diff) | |
| download | kernel-7241c886a71797cc51efc6fadec7076fcf6435c2.tar.gz kernel-7241c886a71797cc51efc6fadec7076fcf6435c2.zip | |
fbdev: hyperv_fb: iounmap() the correct memory when removing a device
When a Hyper-V framebuffer device is removed, or the driver is unbound
from a device, any allocated and/or mapped memory must be released. In
particular, MMIO address space that was mapped to the framebuffer must
be unmapped. Current code unmaps the wrong address, resulting in an
error like:
[ 4093.980597] iounmap: bad address 00000000c936c05c
followed by a stack dump.
Commit d21987d709e8 ("video: hyperv: hyperv_fb: Support deferred IO for
Hyper-V frame buffer driver") changed the kind of address stored in
info->screen_base, and the iounmap() call in hvfb_putmem() was not
updated accordingly.
Fix this by updating hvfb_putmem() to unmap the correct address.
Fixes: d21987d709e8 ("video: hyperv: hyperv_fb: Support deferred IO for Hyper-V frame buffer driver")
Signed-off-by: Michael Kelley <[email protected]>
Reviewed-by: Saurabh Sengar <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Wei Liu <[email protected]>
Message-ID: <[email protected]>
Diffstat (limited to 'tools/testing/selftests/kvm/x86/nested_exceptions_test.c')
0 files changed, 0 insertions, 0 deletions