From: "Eelco Chaudron" <echaudro@redhat.com>
To: "Wang Hai" <wanghai38@huawei.com>
Cc: pshelar@ovn.org, davem@davemloft.net, kuba@kernel.org,
dev@openvswitch.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] openvswitch: fix error return code in validate_and_copy_dec_ttl()
Date: Fri, 04 Dec 2020 13:07:48 +0100 [thread overview]
Message-ID: <40A832BA-4065-4FB2-9C33-D41CF4B336CF@redhat.com> (raw)
In-Reply-To: <20201204114314.1596-1-wanghai38@huawei.com>
On 4 Dec 2020, at 12:43, Wang Hai wrote:
> Fix to return a negative error code from the error handling
> case instead of 0, as done elsewhere in this function.
>
> Changing 'return start' to 'return action_start' can fix this bug.
>
> Fixes: 69929d4c49e1 ("net: openvswitch: fix TTL decrement action
> netlink message format")
> Reported-by: Hulk Robot <hulkci@huawei.com>
> Signed-off-by: Wang Hai <wanghai38@huawei.com>
Thanks for fixing!
Reviewed-by: Eelco Chaudron <echaudro@redhat.com>
> ---
> net/openvswitch/flow_netlink.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/net/openvswitch/flow_netlink.c
> b/net/openvswitch/flow_netlink.c
> index ec0689ddc635..4c5c2331e764 100644
> --- a/net/openvswitch/flow_netlink.c
> +++ b/net/openvswitch/flow_netlink.c
> @@ -2531,7 +2531,7 @@ static int validate_and_copy_dec_ttl(struct net
> *net,
>
> action_start = add_nested_action_start(sfa, OVS_DEC_TTL_ATTR_ACTION,
> log);
> if (action_start < 0)
> - return start;
> + return action_start;
>
> err = __ovs_nla_copy_actions(net, actions, key, sfa, eth_type,
> vlan_tci, mpls_label_count, log);
> --
> 2.17.1
next prev parent reply other threads:[~2020-12-04 12:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-04 11:43 [PATCH net] openvswitch: fix error return code in validate_and_copy_dec_ttl() Wang Hai
2020-12-04 12:07 ` Eelco Chaudron [this message]
2020-12-04 23:44 ` Jakub Kicinski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40A832BA-4065-4FB2-9C33-D41CF4B336CF@redhat.com \
--to=echaudro@redhat.com \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pshelar@ovn.org \
--cc=wanghai38@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).