netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Bastian Bittorf <bb@npl.de>, Ben Greear <greearb@candelatech.com>
Cc: netdev <netdev@vger.kernel.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: 'iw events' stops receiving events after a while on 4.9 + hacks
Date: Wed, 17 May 2017 15:30:35 +0200	[thread overview]
Message-ID: <1495027835.2442.13.camel@sipsolutions.net> (raw)
In-Reply-To: <20170517100844.GC2849@medion.lan> (sfid-20170517_120840_185521_D3BC3321)

On Wed, 2017-05-17 at 12:08 +0200, Bastian Bittorf wrote:
> * Ben Greear <greearb@candelatech.com> [17.05.2017 11:51]:
> > I have been keeping an 'iw events' program running with a perl
> > script gathering its
> > output and post-processing it.  This has been working for several
> > years on 4.7 and earlier
> > kernels, but when testing on 4.9 overnight, I notice that 'iw
> > events' is not showing any input.  'strace' shows
> > that it is waiting on recvmsg.  If I start a second 'iw events'
> > then it will get
> > wifi events as expected.
> 
> me too, also seen on 4.4 - i'am happy for debug ideas.

I've never seen this.

Does it happen when it's very long-running? Or when there are lots of
events?

Perhaps something in the socket buffer accounting is going wrong, so
that it's slowly decreasing to 0?

johannes

  reply	other threads:[~2017-05-17 13:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-16 17:12 'iw events' stops receiving events after a while on 4.9 + hacks Ben Greear
     [not found] ` <d82d191e-8ede-68c6-c9e0-c381dc874d36-my8/4N5VtI7c+919tysfdA@public.gmane.org>
2017-05-17 10:08   ` Bastian Bittorf
2017-05-17 13:30     ` Johannes Berg [this message]
2017-05-17 15:22       ` Ben Greear
2017-05-30 13:18         ` Johannes Berg
     [not found]           ` <1496150322.3327.9.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2017-05-31  8:18             ` Bastian Bittorf
2017-05-31 13:46               ` Ben Greear
2017-05-17 18:34       ` Bastian Bittorf

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=1495027835.2442.13.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=bb@npl.de \
    --cc=greearb@candelatech.com \
    --cc=linux-wireless@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).