[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87ttjywxv5.wl-tiwai@suse.de>
Date: Thu, 18 Apr 2024 16:26:22 +0200
From: Takashi Iwai <tiwai@...e.de>
To: Nam Cao <namcao@...utronix.de>
Cc: Harshit Mogalapalli <harshit.m.mogalapalli@...cle.com>,
jayalk@...works.biz,
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()
On Thu, 18 Apr 2024 16:06:52 +0200,
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.
Note that it was already known that using flush_delayed_work() caused
a problem. See the thread of the fix patch:
https://lore.kernel.org/all/20230129082856.22113-1-tiwai@suse.de/
BTW, the problem is seen with bochs drm.
Takashi
Powered by blists - more mailing lists