fbsplash: use virtual y size in mmap size calculations
The virtual y can be larger - and we can be even writing there since we are taking into account the y offset. Avoids possible crash. But use it only if set, seems it is not set if virtual area is not allocated (though, often fbcon allocates some scrollback area). Signed-off-by: Timo Teräs <timo.teras@iki.fi> Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>
This commit is contained in:
parent
cddc98eab7
commit
82c2fad26c
@ -150,7 +150,7 @@ static void fb_open(const char *strfb_device)
|
||||
|
||||
// map the device in memory
|
||||
G.addr = mmap(NULL,
|
||||
G.scr_var.yres * G.scr_fix.line_length,
|
||||
(G.scr_var.yres_virtual ?: G.scr_var.yres) * G.scr_fix.line_length,
|
||||
PROT_WRITE, MAP_SHARED, fbfd, 0);
|
||||
if (G.addr == MAP_FAILED)
|
||||
bb_perror_msg_and_die("mmap");
|
||||
|
Loading…
Reference in New Issue
Block a user