[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAM_iQpVWSJ8BdRoLDX0MdiqmJn2dp+U9JM4mcfzRbVn4MZbzcg@mail.gmail.com>
Date: Tue, 11 May 2021 10:00:43 -0700
From: Cong Wang <xiyou.wangcong@...il.com>
To: Rocco yue <rocco.yue@...iatek.com>
Cc: "David S . Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Matthias Brugger <matthias.bgg@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Masahiro Yamada <masahiroy@...nel.org>,
Nick Desaulniers <ndesaulniers@...gle.com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Peter Zijlstra <peterz@...radead.org>,
Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>,
LKML <linux-kernel@...r.kernel.org>,
Linux Kernel Network Developers <netdev@...r.kernel.org>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
linux-mediatek@...ts.infradead.org, wsd_upstream@...iatek.com
Subject: Re: [PATCH][v3] rtnetlink: add rtnl_lock debug log
On Tue, May 11, 2021 at 4:46 AM Rocco yue <rocco.yue@...iatek.com> wrote:
>
> From: Rocco Yue <rocco.yue@...iatek.com>
>
> We often encounter system hangs caused by certain process
> holding rtnl_lock for a long time. Even if there is a lock
> detection mechanism in Linux, it is a bit troublesome and
> affects the system performance. We hope to add a lightweight
> debugging mechanism for detecting rtnl_lock.
Any reason why this is specific to RTNL lock? To me holding
a mutex lock for a long time is problematic for any mutex.
I have seen some fs mutex being held for a long time caused
many hung tasks in the system.
Thanks.
Powered by blists - more mailing lists