All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni@redhat.com>
To: Marc Haber <mh+netdev@zugschlus.de>, netdev@vger.kernel.org
Subject: Re: After a while of system running no incoming UDP any more?
Date: Mon, 24 Jul 2017 16:19:10 +0200	[thread overview]
Message-ID: <1500905950.2458.6.camel@redhat.com> (raw)
In-Reply-To: <20170724120901.6bpcieyvn5nccm2l@torres.zugschlus.de>

Hi,

On Mon, 2017-07-24 at 14:09 +0200, Marc Haber wrote:
> Before I begin running older kernels on productive systems, I would like
> to ask wether there have been recent changes in the 4.11 => 4.12
> development cycle that might cause an issue like that.

While there has been some activity regarding the UDP protocol lately,
almost nothing touched UDP in the 4.11 release cycle.

The issue you describe looks similar to the bug fixed by the commit
9bd780f5e066 ("udp: fix poll()"), but the bugged code is only in later
kernels. 

> Any idea what might be happening here and what else I could try?

Once that a system enter the buggy status, do the packets reach the
relevant socket's queue?

ss -u
nstat |grep -e Udp -e Ip

will help checking that.

Thanks,

Paol

  reply	other threads:[~2017-07-24 14:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-24 12:09 After a while of system running no incoming UDP any more? Marc Haber
2017-07-24 14:19 ` Paolo Abeni [this message]
2017-07-25 11:57   ` Marc Haber
2017-07-25 12:17     ` Paolo Abeni
2017-07-26  8:10       ` Marc Haber
2017-07-26  8:33         ` Paolo Abeni
2017-07-28  6:26   ` Marc Haber
2017-07-28  8:05     ` Eric Dumazet
2017-07-28  8:15       ` Paolo Abeni
2017-07-28  8:41         ` Eric Dumazet
2017-07-28  8:07     ` Paolo Abeni
2017-07-28 12:14       ` Marc Haber
2017-08-11 14:34         ` Marc Haber
2017-08-11 20:07           ` Marc Haber

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=1500905950.2458.6.camel@redhat.com \
    --to=pabeni@redhat.com \
    --cc=mh+netdev@zugschlus.de \
    --cc=netdev@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.