linux-kernel - Re: [PATCH v2 net 1/2] vmxnet3: correctly report encapsulated LRO packet

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <Y480KNm16LkG4JX5@kroah.com>
Date:   Tue, 6 Dec 2022 13:23:04 +0100
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Ronak Doshi <doshir@...are.com>
Cc:     netdev@...r.kernel.org, stable@...r.kernel.org,
        VMware PV-Drivers Reviewers <pv-drivers@...are.com>,
        "David S. Miller" <davem@...emloft.net>,
        Eric Dumazet <edumazet@...gle.com>,
        Jakub Kicinski <kuba@...nel.org>,
        Paolo Abeni <pabeni@...hat.com>,
        open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 net  1/2] vmxnet3: correctly report encapsulated LRO
 packet

On Mon, Dec 05, 2022 at 02:42:54PM -0800, Ronak Doshi wrote:
> Commit dacce2be3312 ("vmxnet3: add geneve and vxlan tunnel offload
> support") added support for encapsulation offload. However, the
> pathc did not report correctly the encapsulated packet which is
> LRO'ed by the hypervisor.
> 
> This patch fixes this issue by using correct callback for the LRO'ed
> encapsulated packet.
> 
> Fixes: dacce2be3312 ("vmxnet3: add geneve and vxlan tunnel offload support")
> Signed-off-by: Ronak Doshi <doshir@...are.com>
> Acked-by: Guolin Yang <gyang@...are.com>
> ---
>  drivers/net/vmxnet3/vmxnet3_drv.c | 11 +++++++++--
>  1 file changed, 9 insertions(+), 2 deletions(-)
> 

<formletter>

This is not the correct way to submit patches for inclusion in the
stable kernel tree.  Please read:
    https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.

</formletter>