From: "Mantas Mikulėnas" <grawity@gmail.com>
To: netdev@vger.kernel.org
Cc: Andrei Vagin <avagin@openvz.org>,
"David S. Miller" <davem@davemloft.net>
Subject: regression (4.10) - interface remove uevents not generated
Date: Sat, 11 Mar 2017 17:10:22 +0200 [thread overview]
Message-ID: <d519f10b-8512-efa2-03a1-81f6e4a91c7c@gmail.com> (raw)
Hello,
It seems that commit 002d8a1a6c11b9b2a8ac615095589111dd52749b ("net:
skip genenerating uevents for network namespaces that are exiting")
broke 'remove' uevents for *all* network interfaces, even for those in
the main/default namespace.
Other than breaking some of my udev rules, this also causes problems for
NetworkManager, which apparently relies on those uevents to update its
interface information cache. (I ended up reverting that commit locally
just so I could connect to VPNs again.)
This problem is present in both v4.10.1 and current master
(v4.11-rc1-290-g434fd6353b4c).
--
Mantas Mikulėnas <grawity@gmail.com>
next reply other threads:[~2017-03-11 15:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-11 15:10 Mantas Mikulėnas [this message]
2017-03-11 19:50 ` regression (4.10) - interface remove uevents not generated Andrei Vagin
2017-03-11 21:24 ` Mantas Mikulėnas
2017-03-12 6:51 ` Andrei Vagin
2017-03-12 10:55 ` Mantas Mikulėnas
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=d519f10b-8512-efa2-03a1-81f6e4a91c7c@gmail.com \
--to=grawity@gmail.com \
--cc=avagin@openvz.org \
--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).