From: David Ahern <dsahern@gmail.com>
To: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Network Development <netdev@vger.kernel.org>,
Thomas Haller <thaller@redhat.com>
Subject: Re: [PATCH net-next] veth: report NEWLINK event when moving the peer device in a new namespace
Date: Sat, 1 Sep 2018 17:45:57 -0600 [thread overview]
Message-ID: <247de7c5-5046-81f4-d0b9-f6fcd505e8e8@gmail.com> (raw)
In-Reply-To: <CAJ0CqmV5+qG_L57UC47cUfAuvrnDesk0uhYbsEYy8F7zJ0869A@mail.gmail.com>
On 9/1/18 3:05 AM, Lorenzo Bianconi wrote:
>
> I was thinking about the commit 38e01b30563a and then I realized I
> misread the code
> yesterday. The commit 38e01b30563a provides all relevant info but it
> emits the event
> for veth1 (the device moved in the new namespace).
> An userspace application will not receive that message if it filters
> events for just
> a specific device (veth0 in this case) despite that some device
> properties have changed
> (since veth0 and veth1 are paired devices). To fix that behavior in
> veth_notify routine
> I emits a RTM_NEWLINK event for veth0.
Userspace is managing a veth a pair. It moves one of them to a new
namespace and decides to filter messages related to that device before
the move. If it did not filter the DELLINK message it would get the
information you want. That to me is a userspace problem. What am I missing?
Fundamentally, your proposal means 3 messages when moving a device to a
new namespace which is what I think is unnecessary.
next prev parent reply other threads:[~2018-09-02 3:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1535712096.git.lorenzo.bianconi@redhat.com>
2018-08-31 11:43 ` [PATCH net-next] veth: report NEWLINK event when moving the peer device in a new namespace Lorenzo Bianconi
2018-08-31 15:24 ` David Ahern
2018-08-31 16:19 ` Lorenzo Bianconi
2018-08-31 16:21 ` David Ahern
2018-08-31 16:54 ` Lorenzo Bianconi
2018-09-01 9:05 ` Lorenzo Bianconi
2018-09-01 23:45 ` David Ahern [this message]
2018-09-03 9:10 ` Thomas Haller
2018-09-04 2:54 ` David Ahern
2018-09-07 18:52 ` Thomas Haller
2018-09-09 1:16 ` David Ahern
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=247de7c5-5046-81f4-d0b9-f6fcd505e8e8@gmail.com \
--to=dsahern@gmail.com \
--cc=davem@davemloft.net \
--cc=lorenzo.bianconi@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=thaller@redhat.com \
/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.