From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: davej@codemonkey.org.uk, daniel@iogearbox.net,
alexei.starovoitov@gmail.com, dledford@redhat.com,
netdev@vger.kernel.org
Subject: Re: 4.4-rc7 failure report
Date: Wed, 30 Dec 2015 12:50:03 -0500 (EST) [thread overview]
Message-ID: <20151230.125003.301825767708169401.davem@davemloft.net> (raw)
In-Reply-To: <1451494525.8255.21.camel@edumazet-glaptop2.roam.corp.google.com>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Wed, 30 Dec 2015 11:55:25 -0500
> On Wed, 2015-12-30 at 10:11 -0500, Dave Jones wrote:
>> On Wed, Dec 30, 2015 at 10:38:56AM +0100, Daniel Borkmann wrote:
>>
>> > Given that this drop doesn't strictly need to be caused by filter code,
>> > it would be nice if you could pin the location down where the packet gets
>> > dropped exactly. Perhaps dropwatch or perf with '-e skb:kfree_skb -a -g
>> > dhclient <iface>', etc could help to get a first overview to dig into
>> > details then.
>>
>> Wild stab in the dark, but..
>> Could this bug be another symptom fixed by http://article.gmane.org/gmane.linux.network/392885 ?
>
> dhclient does not use async io
But the bug causes requests to "LOOK" like async I/O, right?
next prev parent reply other threads:[~2015-12-30 17:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-28 21:53 4.4-rc7 failure report Doug Ledford
2015-12-28 22:20 ` Daniel Borkmann
2015-12-29 1:26 ` Doug Ledford
2015-12-30 3:43 ` Alexei Starovoitov
2015-12-30 3:44 ` Doug Ledford
2015-12-30 4:16 ` Alexei Starovoitov
2015-12-30 9:38 ` Daniel Borkmann
2015-12-30 15:11 ` Dave Jones
2015-12-30 16:55 ` Eric Dumazet
2015-12-30 17:50 ` David Miller [this message]
2015-12-30 18:47 ` Doug Ledford
2015-12-30 19:08 ` Eric Dumazet
2015-12-31 2:02 ` Doug Ledford
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=20151230.125003.301825767708169401.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexei.starovoitov@gmail.com \
--cc=daniel@iogearbox.net \
--cc=davej@codemonkey.org.uk \
--cc=dledford@redhat.com \
--cc=eric.dumazet@gmail.com \
--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).