linux-kernel - [BUG] cc5b114dcf bpf, i40e: add meta data support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20180612161739.GA3303@localhost.localdomain>
Date:   Tue, 12 Jun 2018 10:17:39 -0600
From:   Keith Busch <keith.busch@...ux.intel.com>
To:     intel-gfx@...ts.freedesktop.org,
        Daniel Borkmann <daniel@...earbox.net>,
        John Fastabend <john.fastabend@...il.com>,
        Jeff Kirsher <jeffrey.t.kirsher@...el.com>,
        linux-kernel@...r.kernel.org
Subject: [BUG] cc5b114dcf bpf, i40e: add meta data support

My server's i40e no longer obtains an IP address on linux
mainline. Bisected to the following:

commit cc5b114dcf986bfd8e4c37bf65d1b7b1e5290ac6
Author: Daniel Borkmann <daniel@...earbox.net>
Date:   Mon May 28 11:07:20 2018 +0200

    bpf, i40e: add meta data support

Reverting on mainline resolves the issue.

Is there something wrong with my i40e adapter, or is the patch possibly
doing something wrong? Or any other information I can get to help
understand why it's stopped working with this feature?

An excert from "journalctl -xe" on on the failing network adapter
is below.

Thanks,
Keith

---
Jun 12 10:04:35 localhost.localdomain dhclient[2632]: DHCPDISCOVER on eno1 to 255.255.255.255 port 67 interval 7 (xid=0x3b301712)
Jun 12 10:04:42 localhost.localdomain dhclient[2632]: DHCPDISCOVER on eno1 to 255.255.255.255 port 67 interval 14 (xid=0x3b301712)
Jun 12 10:04:56 localhost.localdomain dhclient[2632]: DHCPDISCOVER on eno1 to 255.255.255.255 port 67 interval 21 (xid=0x3b301712)
Jun 12 10:05:03 localhost.localdomain NetworkManager[2215]: <warn>  [1528819503.2274] dhcp4 (eno1): request timed out
Jun 12 10:05:03 localhost.localdomain NetworkManager[2215]: <info>  [1528819503.2275] dhcp4 (eno1): state changed unknown -> timeout
Jun 12 10:05:03 localhost.localdomain NetworkManager[2215]: <info>  [1528819503.2440] dhcp4 (eno1): canceled DHCP transaction, DHCP client pid 2632
Jun 12 10:05:03 localhost.localdomain NetworkManager[2215]: <info>  [1528819503.2441] dhcp4 (eno1): state changed timeout -> done
Jun 12 10:05:03 localhost.localdomain NetworkManager[2215]: <info>  [1528819503.2445] device (eno1): state change: ip-config -> failed (reason 'ip-config-unavailable', internal state 'managed')
Jun 12 10:05:03 localhost.localdomain NetworkManager[2215]: <info>  [1528819503.2448] manager: NetworkManager state is now DISCONNECTED
Jun 12 10:05:03 localhost.localdomain NetworkManager[2215]: <warn>  [1528819503.2452] device (eno1): Activation: failed for connection 'Wired connection 1'
Jun 12 10:05:03 localhost.localdomain NetworkManager[2215]: <info>  [1528819503.2460] device (eno1): state change: failed -> disconnected (reason 'none', internal state 'managed')
Jun 12 10:05:03 localhost.localdomain NetworkManager[2215]: <info>  [1528819503.2498] policy: auto-activating connection 'Wired connection 1'
Jun 12 10:05:03 localhost.localdomain NetworkManager[2215]: <info>  [1528819503.2517] device (eno1): Activation: starting connection 'Wired connection 1' (16a13ab5-c51e-361b-90bc-b6fc6f84cbe9)
Jun 12 10:05:03 localhost.localdomain NetworkManager[2215]: <info>  [1528819503.2520] device (eno1): state change: disconnected -> prepare (reason 'none', internal state 'managed')
Jun 12 10:05:03 localhost.localdomain NetworkManager[2215]: <info>  [1528819503.2523] manager: NetworkManager state is now CONNECTING
Jun 12 10:05:03 localhost.localdomain NetworkManager[2215]: <info>  [1528819503.2529] device (eno1): state change: prepare -> config (reason 'none', internal state 'managed')