From: Doug Ledford <dledford@redhat.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Daniel Borkmann <daniel@iogearbox.net>,
David Miller <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>
Subject: Re: 4.4-rc7 failure report
Date: Tue, 29 Dec 2015 22:44:31 -0500 [thread overview]
Message-ID: <5683531F.9000704@redhat.com> (raw)
In-Reply-To: <20151230034300.GA8670@ast-mbp.thefacebook.com>
[-- Attachment #1: Type: text/plain, Size: 2261 bytes --]
On 12/29/2015 10:43 PM, Alexei Starovoitov wrote:
> On Mon, Dec 28, 2015 at 08:26:44PM -0500, Doug Ledford wrote:
>> On 12/28/2015 05:20 PM, Daniel Borkmann wrote:
>>> On 12/28/2015 10:53 PM, Doug Ledford wrote:
>>>> The 4.4-rc7 kernel is failing for me. In my case, all of my vlan
>>>> interfaces are failing to obtain a dhcp address using dhclient. I've
>>>> tried a hand built 4.4-rc7, and the Fedora rawhide 4.4-rc7 kernel, both
>>>> failed. I've tried NetworkManager and the old SysV network service,
>>>> both fail. I tried a working dhclient from rhel7 on the Fedora rawhide
>>>> install and it failed too. Running tcpdump on the interface shows the
>>>> dhcp request going out, and a dhcp response coming back in. Running
>>>> strace on dhclient shows that it writes the dhcp request, but it never
>>>> recvs a dhcp response. If I manually bring the interface up with a
>>>> static IP address then I'm able to run typical IP traffic across the
>>>> link (aka, ping). It would seem that when dhclient registers a packet
>>>> filter on the socket, that filter is preventing it from ever getting the
>>>> dhcp response. The same dhclient works on any non-vlan interfaces in
>>>> the system, so the filter must work for non-vlan interfaces. Aside from
>>>> the fact that the interface is a vlan, we also use a priority egress map
>>>> on the interface, and we use PFC flow control. Let me know if you need
>>>> anymore to debug the issue, or email me off list and I can get you
>>>> logins to my reproducer machines.
>>>
>>> When you say 4.4-rc7 kernel is failing for you, what latest kernel version
>>> was working, where the socket filter was properly receiving the response on
>>> your vlan iface?
>>
>> v4.3 final works. I haven't bisected where in the 4.4 series it quits
>> working. I can do that tomorrow.
>
> I've tried to reproduce, but cannot seem to make dnsmasq work properly
> over vlan, so bisect would be great.
>
Yeah, I've been working on it. Issues with available machines that
reproduce combined with what hardware they have and whether or not that
hardware works at various steps in the bisection :-/
--
Doug Ledford <dledford@redhat.com>
GPG KeyID: 0E572FDD
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 884 bytes --]
next prev parent reply other threads:[~2015-12-30 3:44 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 [this message]
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
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=5683531F.9000704@redhat.com \
--to=dledford@redhat.com \
--cc=alexei.starovoitov@gmail.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--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).