[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACT4Y+Y-5B2n3ccHMzPro1dD-30ZiGnZ9Zy59aT8iVKjvHemxA@mail.gmail.com>
Date: Thu, 11 Oct 2018 14:11:29 +0200
From: Dmitry Vyukov <dvyukov@...gle.com>
To: Ying Xue <ying.xue@...driver.com>
Cc: Jon Maloy <jon.maloy@...csson.com>,
David Miller <davem@...emloft.net>,
netdev <netdev@...r.kernel.org>,
tipc-discussion@...ts.sourceforge.net,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: net/tipc: recursive locking in tipc_link_reset
On Thu, Oct 11, 2018 at 2:03 PM, Ying Xue <ying.xue@...driver.com> wrote:
>>> Hi,
>>>
>>> I am getting the following error while booting the latest kernel on
>>> bb2d8f2f61047cbde08b78ec03e4ebdb01ee5434 (Oct 10). Config is attached.
>>>
>>> Since this happens during boot, this makes LOCKDEP completely
>>> unusable, does not allow to discover any other locking issues and
>>> masks all new bugs being introduced into kernel.
>>> Please fix asap.
>>> Thanks
>> -parthasarathy.bhuvaragan address as it gives me bounces
>> but this is highly likely due to:
>>
>> commit 3f32d0be6c16b902b687453c962d17eea5b8ea19
>> Author: Parthasarathy Bhuvaragan
>> Date: Tue Sep 25 22:09:10 2018 +0200
>>
>> tipc: lock wakeup & inputq at tipc_link_reset()
>>
>>
>
> Dmitry, I agree with you. The complaint should be caused by the commit
> above. Please try to verify the patch:
> https://patchwork.ozlabs.org/patch/982447.
I trust you for testing ;)
Thanks for the quick fix!
Powered by blists - more mailing lists