Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Tue, 20 Jul 2021 11:58:22 +0200
From:   Greg KH <gregkh@linuxfoundation.org>
To:     Georgi Valkov <gvalkov@abv.bg>
Cc:     davem@davemloft.net, kuba@kernel.org, mhabets@solarflare.com,
        luc.vanoostenryck@gmail.com, snelson@pensando.io, mst@redhat.com,
        linux-usb@vger.kernel.org, netdev@vger.kernel.org,
        linux-kernel@vger.kernel.org, corsac@corsac.net,
        matti.vuorela@bitfactor.fi, stable@vger.kernel.org
Subject: Re: ipheth: fix EOVERFLOW in ipheth_rcvbulk_callback
Message-ID: <YPaePrgEhhaHZAOT@kroah.com>
References: <B60B8A4B-92A0-49B3-805D-809A2433B46C@abv.bg>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <B60B8A4B-92A0-49B3-805D-809A2433B46C@abv.bg>
Precedence: bulk

On Tue, Jul 20, 2021 at 12:37:43PM +0300, Georgi Valkov wrote:
> ipheth: fix EOVERFLOW in ipheth_rcvbulk_callback
> https://github.com/openwrt/openwrt/pull/4084
> 
> 
> From dd109ded2b526636fff438d33433ab64ffd21583 Mon Sep 17 00:00:00 2001
> From: Georgi Valkov <gvalkov@abv.bg>
> Date: Fri, 16 Apr 2021 20:44:36 +0300
> Subject: [PATCH] ipheth: fix EOVERFLOW in ipheth_rcvbulk_callback
> 
> When rx_buf is allocated we need to account for IPHETH_IP_ALIGN,
> which reduces the usable size by 2 bytes. Otherwise we have 1512
> bytes usable instead of 1514, and if we receive more than 1512
> bytes, ipheth_rcvbulk_callback is called with status -EOVERFLOW,
> after which the driver malfunctiones and all communication stops.
> 
> Fixes: ipheth 2-1:4.2: ipheth_rcvbulk_callback: urb status: -75
> 
> Signed-off-by: Georgi Valkov <gvalkov@abv.bg>
> ---
>  drivers/net/usb/ipheth.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 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>