Re: [PATCH v2] fbdev: fix incorrect address computation in deferred IO

2024-04-23 Thread Harshit Mogalapalli
Hi Nam, On 23/04/24 19:04, Nam Cao wrote: On Tue, Apr 23, 2024 at 06:56:52PM +0530, Harshit Mogalapalli wrote: Thanks everyone! I have tested the patched kernel with the syzkaller reproducer and couldn't see a problem. If you want to take credit for testing it, send us: Tested-by: Y

Re: [PATCH v2] fbdev: fix incorrect address computation in deferred IO

2024-04-23 Thread Nam Cao
On Tue, Apr 23, 2024 at 06:56:52PM +0530, Harshit Mogalapalli wrote: > Thanks everyone! > > I have tested the patched kernel with the syzkaller reproducer and couldn't > see a problem. If you want to take credit for testing it, send us: Tested-by: Your Name And that tag will appear in

Re: [PATCH v2] fbdev: fix incorrect address computation in deferred IO

2024-04-23 Thread Harshit Mogalapalli
Hi, On 23/04/24 18:37, Thomas Zimmermann wrote: Hi Am 23.04.24 um 13:50 schrieb Nam Cao: With deferred IO enabled, a page fault happens when data is written to the framebuffer device. Then driver determines which page is being updated by calculating the offset of the written virtual address w

Re: [PATCH v2] fbdev: fix incorrect address computation in deferred IO

2024-04-23 Thread Thomas Zimmermann
Hi Am 23.04.24 um 13:50 schrieb Nam Cao: With deferred IO enabled, a page fault happens when data is written to the framebuffer device. Then driver determines which page is being updated by calculating the offset of the written virtual address within the virtual memory area, and uses this offset

[PATCH v2] fbdev: fix incorrect address computation in deferred IO

2024-04-23 Thread Nam Cao
With deferred IO enabled, a page fault happens when data is written to the framebuffer device. Then driver determines which page is being updated by calculating the offset of the written virtual address within the virtual memory area, and uses this offset to get the updated page within the internal