[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240419182313.3f36ac0b@namcao>
Date: Fri, 19 Apr 2024 18:23:13 +0200
From: Nam Cao <namcao@...utronix.de>
To: Harshit Mogalapalli <harshit.m.mogalapalli@...cle.com>
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 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.
> 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?
Best regards,
Nam
Powered by blists - more mailing lists