[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Z1fYeNSdnyJniJSo@pop-os.localdomain>
Date: Mon, 9 Dec 2024 21:58:16 -0800
From: Cong Wang <xiyou.wangcong@...il.com>
To: Dan Carpenter <dan.carpenter@...aro.org>
Cc: Cong Wang <cong.wang@...edance.com>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
Simon Horman <horms@...nel.org>,
Kuniyuki Iwashima <kuniyu@...zon.com>,
Ido Schimmel <idosch@...dia.com>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org
Subject: Re: [PATCH net-next] rtnetlink: fix error code in rtnl_newlink()
On Fri, Dec 06, 2024 at 03:32:52PM +0300, Dan Carpenter wrote:
> If rtnl_get_peer_net() fails, then propagate the error code. Don't
> return success.
>
> Fixes: 48327566769a ("rtnetlink: fix double call of rtnl_link_get_net_ifla()")
> Signed-off-by: Dan Carpenter <dan.carpenter@...aro.org>
Oops, how could I miss this even when I mentioned propagation in my commit
message... :-/
Thanks for catching it quickly!
Powered by blists - more mailing lists