From: Ilya Maximets <i.maximets@ovn.org>
To: Tao Liu <thomas.liu@ucloud.cn>, pshelar@ovn.org
Cc: dev@openvswitch.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, i.maximets@ovn.org,
jean.tourrilhes@hpe.com, kuba@kernel.org, davem@davemloft.net,
wenxu@ucloud.cn
Subject: Re: [ovs-dev] [PATCH net v2] openvswitch: meter: fix race when getting now_ms.
Date: Thu, 13 May 2021 16:35:47 +0200 [thread overview]
Message-ID: <f26c37b5-487c-0399-e65b-e0a9d2259c03@ovn.org> (raw)
In-Reply-To: <20210513130800.31913-1-thomas.liu@ucloud.cn>
On 5/13/21 3:08 PM, Tao Liu wrote:
> We have observed meters working unexpected if traffic is 3+Gbit/s
> with multiple connections.
>
> now_ms is not pretected by meter->lock, we may get a negative
> long_delta_ms when another cpu updated meter->used, then:
> delta_ms = (u32)long_delta_ms;
> which will be a large value.
>
> band->bucket += delta_ms * band->rate;
> then we get a wrong band->bucket.
>
> OpenVswitch userspace datapath has fixed the same issue[1] some
> time ago, and we port the implementation to kernel datapath.
>
> [1] https://patchwork.ozlabs.org/project/openvswitch/patch/20191025114436.9746-1-i.maximets@ovn.org/
>
> Fixes: 96fbc13d7e77 ("openvswitch: Add meter infrastructure")
> Signed-off-by: Tao Liu <thomas.liu@ucloud.cn>
> Suggested-by: Ilya Maximets <i.maximets@ovn.org>
> ---
> Changelog:
> v2: just set negative long_delta_ms to zero in case of race for meter lock.
> v1: make now_ms protected by meter lock.
> ---
Thanks!
I didn't test it, but the change looks good to me.
Reviewed-by: Ilya Maximets <i.maximets@ovn.org>
> net/openvswitch/meter.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/net/openvswitch/meter.c b/net/openvswitch/meter.c
> index 96b524c..896b8f5 100644
> --- a/net/openvswitch/meter.c
> +++ b/net/openvswitch/meter.c
> @@ -611,6 +611,14 @@ bool ovs_meter_execute(struct datapath *dp, struct sk_buff *skb,
> spin_lock(&meter->lock);
>
> long_delta_ms = (now_ms - meter->used); /* ms */
> + if (long_delta_ms < 0) {
> + /* This condition means that we have several threads fighting
> + * for a meter lock, and the one who received the packets a
> + * bit later wins. Assuming that all racing threads received
> + * packets at the same time to avoid overflow.
> + */
> + long_delta_ms = 0;
> + }
>
> /* Make sure delta_ms will not be too large, so that bucket will not
> * wrap around below.
>
next prev parent reply other threads:[~2021-05-13 14:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-13 13:08 Tao Liu
2021-05-13 14:35 ` Ilya Maximets [this message]
2021-05-13 23:00 ` patchwork-bot+netdevbpf
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=f26c37b5-487c-0399-e65b-e0a9d2259c03@ovn.org \
--to=i.maximets@ovn.org \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=jean.tourrilhes@hpe.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pshelar@ovn.org \
--cc=thomas.liu@ucloud.cn \
--cc=wenxu@ucloud.cn \
/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
all inboxes | Powered by JetHome®