Bug#1029602: Bug report: kernel oops in vmw_fb_dirty_flush()

2023-01-30 Thread Keyu Tao
Hi Rusin, Thank you for your timely response. I tested that this bug is not reproducible in v6.2-rc5 yesterday. On 1/31/23 03:54, Zack Rusin wrote: On Tue, 2023-01-31 at 00:36 +0800, Keyu Tao wrote: !! External Email Hi vmwgfx maintainers, An out-of-bound access in vmwgfx specific

Bug#1029602: Bug report: kernel oops in vmw_fb_dirty_flush()

2023-01-30 Thread Zack Rusin
On Tue, 2023-01-31 at 00:36 +0800, Keyu Tao wrote: > !! External Email > > Hi vmwgfx maintainers, > > An out-of-bound access in vmwgfx specific framebuffer implementation can > be easily triggered by fbterm (a framebuffer terminal emulator) when it > is going to scroll screen. > > With some

Bug#1029602: Bug report: kernel oops in vmw_fb_dirty_flush()

2023-01-30 Thread Keyu Tao
Hi vmwgfx maintainers, An out-of-bound access in vmwgfx specific framebuffer implementation can be easily triggered by fbterm (a framebuffer terminal emulator) when it is going to scroll screen. With some debugging, it seems that vmw_fb_dirty_flush() cannot handle the vinfo.yoffset