From: Peter Robinson <hidden> Date: 2020-12-29 09:42:50
The info message was showing the mapped address for the framebuffer. To avoid
security problems, all virtual addresses are converted to __ptrval__, so
the message has pointless information:
simple-framebuffer 3ea9b000.framebuffer: framebuffer at 0x3ea9b000, 0x12c000 bytes, mapped to 0x(____ptrval____)
Drop the extraneous bits to clean up the message:
simple-framebuffer 3ea9b000.framebuffer: framebuffer at 0x3ea9b000, 0x12c000 bytes
Signed-off-by: Peter Robinson <redacted>
---
drivers/video/fbdev/simplefb.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
From: Hans de Goede <hidden> Date: 2020-12-29 13:03:21
Hi,
On 12/28/20 7:39 PM, Peter Robinson wrote:
The info message was showing the mapped address for the framebuffer. To avoid
security problems, all virtual addresses are converted to __ptrval__, so
the message has pointless information:
simple-framebuffer 3ea9b000.framebuffer: framebuffer at 0x3ea9b000, 0x12c000 bytes, mapped to 0x(____ptrval____)
Drop the extraneous bits to clean up the message:
simple-framebuffer 3ea9b000.framebuffer: framebuffer at 0x3ea9b000, 0x12c000 bytes
Signed-off-by: Peter Robinson <redacted>
Thanks, patch looks good to me:
Reviewed-by: Hans de Goede <redacted>
Regards,
Hans
From: Daniel Vetter <hidden> Date: 2021-01-07 17:05:06
Hi Hans,
On Tue, Dec 29, 2020 at 02:02:30PM +0100, Hans de Goede wrote:
Hi,
On 12/28/20 7:39 PM, Peter Robinson wrote:
quoted
The info message was showing the mapped address for the framebuffer. To avoid
security problems, all virtual addresses are converted to __ptrval__, so
the message has pointless information:
simple-framebuffer 3ea9b000.framebuffer: framebuffer at 0x3ea9b000, 0x12c000 bytes, mapped to 0x(____ptrval____)
Drop the extraneous bits to clean up the message:
simple-framebuffer 3ea9b000.framebuffer: framebuffer at 0x3ea9b000, 0x12c000 bytes
Signed-off-by: Peter Robinson <redacted>
Thanks, patch looks good to me:
Reviewed-by: Hans de Goede <redacted>
Since you have commit rights for drm-misc I'm assuming you're also going
to push this one?
Thanks, Daniel
From: Hans de Goede <hidden> Date: 2021-01-20 11:16:14
Hi,
On 1/7/21 6:04 PM, Daniel Vetter wrote:
Hi Hans,
On Tue, Dec 29, 2020 at 02:02:30PM +0100, Hans de Goede wrote:
quoted
Hi,
On 12/28/20 7:39 PM, Peter Robinson wrote:
quoted
The info message was showing the mapped address for the framebuffer. To avoid
security problems, all virtual addresses are converted to __ptrval__, so
the message has pointless information:
simple-framebuffer 3ea9b000.framebuffer: framebuffer at 0x3ea9b000, 0x12c000 bytes, mapped to 0x(____ptrval____)
Drop the extraneous bits to clean up the message:
simple-framebuffer 3ea9b000.framebuffer: framebuffer at 0x3ea9b000, 0x12c000 bytes
Signed-off-by: Peter Robinson <redacted>
Thanks, patch looks good to me:
Reviewed-by: Hans de Goede <redacted>
Since you have commit rights for drm-misc I'm assuming you're also going
to push this one?
I knew there was some discussion about using drm-misc for drivers/video/fbdev stuff
but I missed that it was decided to go ahead with that.
Good to know that this is handled through drm-misc now.
I've pushed this patch to drm-misc-next.
Regards,
Hans
From: Daniel Vetter <hidden> Date: 2021-01-20 11:27:01
On Wed, Jan 20, 2021 at 12:16 PM Hans de Goede [off-list ref] wrote:
Hi,
On 1/7/21 6:04 PM, Daniel Vetter wrote:
quoted
Hi Hans,
On Tue, Dec 29, 2020 at 02:02:30PM +0100, Hans de Goede wrote:
quoted
Hi,
On 12/28/20 7:39 PM, Peter Robinson wrote:
quoted
The info message was showing the mapped address for the framebuffer. To avoid
security problems, all virtual addresses are converted to __ptrval__, so
the message has pointless information:
simple-framebuffer 3ea9b000.framebuffer: framebuffer at 0x3ea9b000, 0x12c000 bytes, mapped to 0x(____ptrval____)
Drop the extraneous bits to clean up the message:
simple-framebuffer 3ea9b000.framebuffer: framebuffer at 0x3ea9b000, 0x12c000 bytes
Signed-off-by: Peter Robinson <redacted>
Thanks, patch looks good to me:
Reviewed-by: Hans de Goede <redacted>
Since you have commit rights for drm-misc I'm assuming you're also going
to push this one?
I knew there was some discussion about using drm-misc for drivers/video/fbdev stuff
but I missed that it was decided to go ahead with that.
Good to know that this is handled through drm-misc now.
This is official since a while:
commit 6a7553e8d84d5322d883cb83bb9888c49a0f04e0
Author: Bartlomiej Zolnierkiewicz [off-list ref]
Date: Fri Aug 9 15:46:40 2019 +0200
MAINTAINERS: handle fbdev changes through drm-misc tree
Cheers, Daniel
I've pushed this patch to drm-misc-next.
Regards,
Hans