From: Eelco Chaudron <echaudro@redhat.com>
To: Ilya Maximets <i.maximets@ovn.org>
Cc: netdev@vger.kernel.org, pshelar@ovn.org, davem@davemloft.net,
dev@openvswitch.org, aconole@redhat.com, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com
Subject: Re: [PATCH net v2] openvswitch: Fix flow lookup to use unmasked key
Date: Thu, 15 Dec 2022 15:36:30 +0100 [thread overview]
Message-ID: <3142B112-D79A-48D2-970A-6B2DF45ACD30@redhat.com> (raw)
In-Reply-To: <920bc474-d5d8-2d8d-d9eb-fd237cba723d@ovn.org>
On 15 Dec 2022, at 12:45, Ilya Maximets wrote:
> On 12/14/22 17:33, Eelco Chaudron wrote:
>> The commit mentioned below causes the ovs_flow_tbl_lookup() function
>> to be called with the masked key. However, it's supposed to be called
>> with the unmasked key.
>
> Hi, Eelco. Thanks for the fix!
>
> Could you, please, add more information to the commit message on
> why this is a problem, with some examples? This will be useful
> for someone in the future trying to understand why we actually
> have to use an unmasked key here.
ACK will add the same description as in the OVS dpif-netdev commit.
> Also, I suppose, 'Cc: stable@vger.kernel.org' tag is needed in the
> commit message since it's a fix for a bug that is actually impacts
> users and needs to be backported.
Will do in the v3.
> Best regards, Ilya Maximets.
>
>>
>> This change reverses the commit below, but rather than having the key
>> on the stack, it's allocated.
>>
>> Fixes: 190aa3e77880 ("openvswitch: Fix Frame-size larger than 1024 bytes warning.")
>>
>> Signed-off-by: Eelco Chaudron <echaudro@redhat.com>
>>
>> ---
>> Version history:
>> - v2: Fixed ENOME(N/M) error. Forgot to do a stg refresh.
>>
>> net/openvswitch/datapath.c | 25 ++++++++++++++++---------
>> 1 file changed, 16 insertions(+), 9 deletions(-)
prev parent reply other threads:[~2022-12-15 14:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 16:33 [PATCH net v2] openvswitch: Fix flow lookup to use unmasked key Eelco Chaudron
2022-12-15 11:45 ` Ilya Maximets
2022-12-15 14:36 ` Eelco Chaudron [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=3142B112-D79A-48D2-970A-6B2DF45ACD30@redhat.com \
--to=echaudro@redhat.com \
--cc=aconole@redhat.com \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=edumazet@google.com \
--cc=i.maximets@ovn.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pshelar@ovn.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