[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <97d8c196-cd11-8859-fc14-ed12191f52af@windriver.com>
Date: Thu, 11 Oct 2018 20:03:28 +0800
From: Ying Xue <ying.xue@...driver.com>
To: Dmitry Vyukov <dvyukov@...gle.com>,
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 10/11/2018 03:59 PM, Dmitry Vyukov wrote:
> On Thu, Oct 11, 2018 at 9:55 AM, Dmitry Vyukov <dvyukov@...gle.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.
Thanks,
Ying
Powered by blists - more mailing lists