diff options
| author | Daniel Kurtz <djkurtz@chromium.org> | 2014-04-04 17:22:01 +0800 |
|---|---|---|
| committer | Inki Dae <daeinki@gmail.com> | 2014-06-02 02:07:02 +0900 |
| commit | 2f1eab8d8ab59e799f7d51d62410b398607a7bc3 (patch) | |
| tree | a35a4e79c415100eaa0af6b66647cfa8da71d3b6 /tools/perf/scripts/python/syscall-counts-by-pid.py | |
| parent | 182407a6ed5333fc37dd980a8de91a8f826a94f6 (diff) | |
drm/exynos/fbdev: don't set fix.smem/mmio_{start,len}
Kernel access to the eyxnos fbdev framebuffer is via its gem object's
kernel mapping (kvaddr, stored in info->screen_base).
User space access is provided by mmap(), read() and write() of /dev/fb/fb0.
These functions also only use screen_base/screen_size().
Therefore, it is not necessary to set fix->smem_{start,len} or
fix->mmio_{start,len} fields.
This avoids leaking kernel, physical and dma mapped addresses to user
space via the ioctls FBIOGET_VSCREENINFO and FBIOGET_FSCREENINFO.
Signed-off-by: Daniel Kurtz <djkurtz@chromium.org>
Signed-off-by: Inki Dae <inki.dae@samsung.com>
Diffstat (limited to 'tools/perf/scripts/python/syscall-counts-by-pid.py')
0 files changed, 0 insertions, 0 deletions