All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 204099] New: systemd-networkd fails on 5.2 - same version works on 5.1.16
Date: Tue, 9 Jul 2019 07:43:44 -0700	[thread overview]
Message-ID: <20190709074344.76049d02@hermes.lan> (raw)

Looks like the stricter netlink validation broke userspace.
This is bad.

Begin forwarded message:

Date: Tue, 09 Jul 2019 00:44:01 +0000
From: bugzilla-daemon@bugzilla.kernel.org
To: stephen@networkplumber.org
Subject: [Bug 204099] New: systemd-networkd fails on 5.2 - same version works on 5.1.16


https://bugzilla.kernel.org/show_bug.cgi?id=204099

            Bug ID: 204099
           Summary: systemd-networkd fails on 5.2 - same version works on
                    5.1.16
           Product: Networking
           Version: 2.5
    Kernel Version: 5.2
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: low
          Priority: P1
         Component: Other
          Assignee: stephen@networkplumber.org
          Reporter: Ian.kumlien@gmail.com
        Regression: No

This is more FYI, I haven't had time to properly debug it.

Booting 5.2 causes systemd-networkd to fail to bring any interface up, it will
fail with: "Could not bring up interface: Invalid argument"

However, booting 5.1.16 with the same software works just fine.

Sounds like something was changed in, what I assume is, the netlink API

-- 
You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2019-07-09 14:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-09 14:43 Stephen Hemminger [this message]
2019-07-10 22:43 ` Fw: [Bug 204099] New: systemd-networkd fails on 5.2 - same version works on 5.1.16 David Ahern
2019-07-11  5:54   ` Leon Romanovsky

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=20190709074344.76049d02@hermes.lan \
    --to=stephen@networkplumber.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 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.