[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1867f98e7951f8d044a7dbf16fcf6a93996914f7.camel@intel.com>
Date: Thu, 3 Dec 2020 17:04:14 +0000
From: "Nguyen, Anthony L" <anthony.l.nguyen@...el.com>
To: "kuba@...nel.org" <kuba@...nel.org>,
"Brandeburg, Jesse" <jesse.brandeburg@...el.com>
CC: "Pawlak, Jakub" <jakub.pawlak@...el.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"intel-wired-lan@...ts.osuosl.org" <intel-wired-lan@...ts.osuosl.org>
Subject: Re: [PATCH net] iavf: fix double-release of rtnl_lock
On Wed, 2020-12-02 at 18:18 -0800, Jakub Kicinski wrote:
> This code does not jump to exit on an error in iavf_lan_add_device(),
> so the rtnl_unlock() from the normal path will follow.
>
> Fixes: b66c7bc1cd4d ("iavf: Refactor init state machine")
> Signed-off-by: Jakub Kicinski <kuba@...nel.org>
> ---
> drivers/net/ethernet/intel/iavf/iavf_main.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
Reviewed-by: Tony Nguyen <anthony.l.nguyen@...el.com>
Did you want to apply this or did you want me to take it?
Powered by blists - more mailing lists