From: Paolo Abeni <pabeni@redhat.com>
To: netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
Mahesh Bandewar <maheshb@google.com>
Subject: Re: [PATCH net-next 1/3] ipvlan: forbid vlan devices on top of ipvlan
Date: Fri, 02 Mar 2018 11:59:06 +0100 [thread overview]
Message-ID: <1519988346.10214.12.camel@redhat.com> (raw)
In-Reply-To: <8532e2ae7917c8eda22fa224efe74c389dfaf213.1519981194.git.pabeni@redhat.com>
On Fri, 2018-03-02 at 11:55 +0100, Paolo Abeni wrote:
> Currently we allow the creation of 8021q devices on top of
> ipvlan, but such devices are nonfunctional, as the underlying
> ipvlan rx_hanlder hook can't match the relevant traffic.
>
> Be explicit and forbid the creation of such nonfunctional devices.
>
> Signed-off-by: Paolo Abeni <pabeni@redhat.com>
Oops.. this is not part of any series. I apologize for the noise, I
will resend with a proper subj.
Cheers,
Paolo
prev parent reply other threads:[~2018-03-02 10:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-02 10:55 [PATCH net-next 1/3] ipvlan: forbid vlan devices on top of ipvlan Paolo Abeni
2018-03-02 10:59 ` Paolo Abeni [this message]
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=1519988346.10214.12.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=davem@davemloft.net \
--cc=maheshb@google.com \
--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).