Re: [PATCH] net: called rtnl_unlock() before runpm resumes devices

2021-04-20 Thread Jakub Kicinski
On Tue, 20 Apr 2021 10:34:17 +0200 Eric Dumazet wrote: > On Tue, Apr 20, 2021 at 9:54 AM AceLan Kao wrote: > > > > From: "Chia-Lin Kao (AceLan)" > > > > The rtnl_lock() has been called in rtnetlink_rcv_msg(), and then in > > __dev_open() it calls pm_runtime_resume() to resume devices, and in > >

Re: [PATCH] net: called rtnl_unlock() before runpm resumes devices

2021-04-20 Thread Eric Dumazet
On Tue, Apr 20, 2021 at 9:54 AM AceLan Kao wrote: > > From: "Chia-Lin Kao (AceLan)" > > The rtnl_lock() has been called in rtnetlink_rcv_msg(), and then in > __dev_open() it calls pm_runtime_resume() to resume devices, and in > some devices' resume function(igb_resum,igc_resume) they calls rtnl_l

[PATCH] net: called rtnl_unlock() before runpm resumes devices

2021-04-20 Thread AceLan Kao
From: "Chia-Lin Kao (AceLan)" The rtnl_lock() has been called in rtnetlink_rcv_msg(), and then in __dev_open() it calls pm_runtime_resume() to resume devices, and in some devices' resume function(igb_resum,igc_resume) they calls rtnl_lock() again. That leads to a recursive lock. It should leave