From: Greg KH <gregkh@linuxfoundation.org>
To: Quan Tian <qtian@vmware.com>
Cc: stable@vger.kernel.org
Subject: Re: IPv6 traffic distribution problem with OVS group on 6.5
Date: Wed, 13 Sep 2023 10:10:57 +0200 [thread overview]
Message-ID: <2023091347-aspirin-lilac-6536@gregkh> (raw)
In-Reply-To: <20230913065407.GA510095@bm02>
On Wed, Sep 13, 2023 at 06:54:07AM +0000, Quan Tian wrote:
> Hi,
>
> We found that OVS group always selected the same bucket for different L4
> flows between two given IPv6 addresses on 6.5. It was because commit
> e069ba07e6c7 ("net: openvswitch: add support for l4 symmetric hashing")
> introduced support for symmetric hashing and used the flow dissector,
> which had a problem that it didn't incorporate transport ports when
> flow label is present in IPv6 header. The bug is fixed by this commit:
>
> a5e2151ff9d5 ("net/ipv6: SKB symmetric hash should incorporate transport ports")
>
> Could you please backport it to 6.5.y?
>
> Issue: https://github.com/antrea-io/antrea/issues/5457
Sure, now queued up.
greg k-h
prev parent reply other threads:[~2023-09-13 8:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 6:54 IPv6 traffic distribution problem with OVS group on 6.5 Quan Tian
2023-09-13 8:10 ` Greg KH [this message]
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=2023091347-aspirin-lilac-6536@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=qtian@vmware.com \
--cc=stable@vger.kernel.org \
/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