[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AM6PR04MB4966FBCF88E707CAC069663680560@AM6PR04MB4966.eurprd04.prod.outlook.com>
Date: Mon, 24 Aug 2020 08:18:56 +0000
From: Aisheng Dong <aisheng.dong@....com>
To: Saravana Kannan <saravanak@...gle.com>,
Dong Aisheng <dongas86@...il.com>
CC: open list <linux-kernel@...r.kernel.org>,
Guenter Roeck <linux@...ck-us.net>,
gregkh <gregkh@...uxfoundation.org>,
Marek Szyprowski <m.szyprowski@...sung.com>,
Naresh Kamboju <naresh.kamboju@...aro.org>,
dl-linux-imx <linux-imx@....com>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@...ts.infradead.org>,
Shawn Guo <shawnguo@...nel.org>,
Sascha Hauer <kernel@...gutronix.de>
Subject: RE: Lockdep warning caused by "driver core: Fix sleeping in invalid
context during device link deletion"
> From: Saravana Kannan <saravanak@...gle.com>
> Sent: Saturday, August 22, 2020 2:28 AM
>
> On Thu, Aug 20, 2020 at 8:50 PM Dong Aisheng <dongas86@...il.com>
> wrote:
> >
> > Hi ALL,
> >
> > We met the below WARNING during system suspend on an iMX6Q SDB board
> > with the latest linus/master branch (v5.9-rc1+) and next-20200820.
> > v5.8 kernel is ok. So i did bisect and finally found it's caused by
> > the patch below.
> > Reverting it can get rid of the warning, but I wonder if there may be
> > other potential issues.
> > Any ideas?
>
> Thanks for the report. I'll look into this more closely after Linux Plumbers (next
> week). We can't just revert the patch you pointed out because it's fixing another
> locking issue.
>
Thanks. Pls have me CCed when you send out patches.
I'd love to test it.
Regards
Aisheng
Powered by blists - more mailing lists