[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ee7a1664-dfe2-41c4-b635-47affec03ce6@oracle.com>
Date: Fri, 19 Apr 2024 22:09:38 +0530
From: Harshit Mogalapalli <harshit.m.mogalapalli@...cle.com>
To: Nam Cao <namcao@...utronix.de>
Cc: 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,
"stable@...r.kernel.org" <stable@...r.kernel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Sasha Levin <sashal@...nel.org>
Subject: Re: [bug-report] task info hung problem in fb_deferred_io_work()
On 19/04/24 21:53, Nam Cao wrote:
> On 2024-04-19 Harshit Mogalapalli wrote:
>> +CC stable( heads up as this is a regression affecting 5.15.y and
>> probably others, Greg: this was reproducible upstream so reported
>> everything w.r.t upstream code but initially found on 5.15.y)
>
> No worry about this, I will add a "Cc: <stable@...r.kernel.org>" tag
> to the patch, and the stable folks (or their scripts) will pick it up.
>
Thanks for that!
>> This patch works well against the reproducer, this simplified repro and
>> the longer repro which syzkaller generated couldn't trigger any hang
>> with the below patch applied.
>
> Great, thanks! Can I add
> Reported-and-tested-by: Harshit Mogalapalli <harshit.m.mogalapalli@...cle.com>
> to the patch?
>
Sure, that would be good!
Thanks,
Harshit
> Best regards,
> Nam
Powered by blists - more mailing lists