All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yves-Alexis Perez <corsac@corsac.net>
To: Georgi Valkov <gvalkov@abv.bg>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
	Jakub Kicinski <kuba@kernel.org>,
	"David S . Miller" <davem@davemloft.net>,
	linux-usb <linux-usb@vger.kernel.org>,
	Linux Netdev List <netdev@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"stable @ vger . kernel . org" <stable@vger.kernel.org>
Subject: Re: [PATCH v2 0/1] ipheth URB overflow fix
Date: Wed, 02 Feb 2022 18:01:07 +0100	[thread overview]
Message-ID: <a29174ef18ac5a4d6be2cc576252f77a7c16b306.camel@corsac.net> (raw)
In-Reply-To: <CE7AE1A3-51E9-45CE-A4EE-DACB03B96D9C@abv.bg>

On Wed, 2022-02-02 at 12:35 +0200, Georgi Valkov wrote:
> Without the patch I get EOVERFLOW and there is no further communication.
> It would be nice if a failsafe mechanism is implemented to recover from
> faults
> like that or in the event that no communication is detected over a certain
> period.
> With the patch applied, everything works fine:
> 1480 bytes from 10.98.8.1: icmp_seq=0 ttl=253 time=50.234 ms

Thanks for the steps. I can confirm that without the patch I get:

[  +4.516398] ipheth 1-3.3:4.2: ipheth_rcvbulk_callback: urb status: -75

and the interface doesn't work anymore.

With the patch applied, I get ping results and the network keeps going.

Regards,
-- 
Yves-Alexis

      reply	other threads:[~2022-02-02 17:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-01  7:16 [PATCH v2 0/1] ipheth URB overflow fix Jan Kiszka
2022-02-01  7:16 ` [PATCH v2 1/1] ipheth: fix EOVERFLOW in ipheth_rcvbulk_callback Jan Kiszka
2022-02-02  4:30 ` [PATCH v2 0/1] ipheth URB overflow fix patchwork-bot+netdevbpf
2022-02-02  8:09 ` Yves-Alexis Perez
2022-02-02 10:35   ` Georgi Valkov
2022-02-02 17:01     ` Yves-Alexis Perez [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=a29174ef18ac5a4d6be2cc576252f77a7c16b306.camel@corsac.net \
    --to=corsac@corsac.net \
    --cc=davem@davemloft.net \
    --cc=gvalkov@abv.bg \
    --cc=jan.kiszka@siemens.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.