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:   Mon, 31 Jan 2022 09:47:04 -0800
From:   Jakub Kicinski <kuba@kernel.org>
To:     Jan Kiszka <jan.kiszka@siemens.com>
Cc:     Georgi Valkov <gvalkov@abv.bg>,
        Greg KH <gregkh@linuxfoundation.org>, <davem@davemloft.net>,
        <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: <20220131094704.0e255169@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
In-Reply-To: <6108f260-36bf-0059-ccb9-8189f4a2d0c1@siemens.com>
References: <B60B8A4B-92A0-49B3-805D-809A2433B46C@abv.bg>
        <20210720122215.54abaf53@cakuba>
        <5D0CFF83-439B-4A10-A276-D2D17B037704@abv.bg>
        <YPa4ZelG2k8Z826E@kroah.com>
        <C6AA954F-8382-461D-835F-E5CA03363D84@abv.bg>
        <YPbHoScEo8ZJyox6@kroah.com>
        <AEC79E3B-FA7F-4A36-95CE-B6D0F3063DF8@abv.bg>
        <80a13e9b-e026-1238-39ed-32deb5ff17b0@siemens.com>
        <20220131092726.3864b19f@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
        <6108f260-36bf-0059-ccb9-8189f4a2d0c1@siemens.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Mon, 31 Jan 2022 18:35:44 +0100 Jan Kiszka wrote:
> On 31.01.22 18:27, Jakub Kicinski wrote:
> > On Mon, 31 Jan 2022 10:45:23 +0100 Jan Kiszka wrote:  
> >> What happened here afterwards?
> >>
> >> I just found out the hard way that this patch is still not in mainline
> >> but really needed.  
> > 
> > I have not seen the repost :(  
> 
> Would it help if I do that on behalf of Georgi? Meanwhile, I can add a 
> tested-by to it, after almost a full working day with it applied.

That's probably the most expedient way to close the issue, yup.
Real Fixes: tag would be useful as well.