[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220304205659.5e0c6997@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date: Fri, 4 Mar 2022 20:56:59 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Vladimir Oltean <vladimir.oltean@....com>
Cc: netdev@...r.kernel.org, "David S. Miller" <davem@...emloft.net>,
Florian Fainelli <f.fainelli@...il.com>,
Andrew Lunn <andrew@...n.ch>,
Vivien Didelot <vivien.didelot@...il.com>,
Vladimir Oltean <olteanv@...il.com>
Subject: Re: [PATCH v2 net-next] net: dsa: unlock the rtnl_mutex when
dsa_master_setup() fails
On Thu, 3 Mar 2022 16:08:40 +0200 Vladimir Oltean wrote:
> Subject: [PATCH v2 net-next] net: dsa: unlock the rtnl_mutex when dsa_master_setup() fails
Did you mean s/-next//?
> After the blamed commit, dsa_tree_setup_master() may exit without
> calling rtnl_unlock(), fix that.
>
> Fixes: c146f9bc195a ("net: dsa: hold rtnl_mutex when calling dsa_master_{setup,teardown}")
> Signed-off-by: Vladimir Oltean <vladimir.oltean@....com>
> ---
> v1->v2: actually propagate the error code instead of always returning 0
Powered by blists - more mailing lists