[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bcd611a0-ee8e-4a89-9783-81c3650b4942@oracle.com>
Date: Fri, 19 Apr 2024 13:05:48 +0530
From: Harshit Mogalapalli <harshit.m.mogalapalli@...cle.com>
To: Nam Cao <namcao@...utronix.de>
Cc: Daniel Vetter <daniel@...ll.ch>, deller@....de,
linux-fbdev@...r.kernel.org, dri-devel@...ts.freedesktop.org,
tiwai@...e.de, bigeasy@...utronix.de, patrik.r.jakobsson@...il.com,
LKML <linux-kernel@...r.kernel.org>,
Vegard Nossum
<vegard.nossum@...cle.com>,
George Kennedy <george.kennedy@...cle.com>,
Darren Kenny <darren.kenny@...cle.com>, chuansheng.liu@...el.com
Subject: Re: [bug-report] task info hung problem in fb_deferred_io_work()
Hi Nam,
On 18/04/24 19:36, Nam Cao wrote:
> On 2024-04-18 Harshit Mogalapalli wrote:
>> While fuzzing 5.15.y kernel with Syzkaller, we noticed a INFO: task hung
>> bug in fb_deferred_io_work()
>
> Which framebuffer device are you using exactly? It is possible that
> the problem is with the device driver, not core framebuffer.
>
I am not very sure about the answer, but the C reproducer uses(/dev/fb0)
int fd = open("/dev/fb0", O_RDWR, 0);
Thanks,
Harshit
> Best regards,
> Nam
Powered by blists - more mailing lists