All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
	Eric Dumazet <eric.dumazet@gmail.com>,
	Anna Fischer <anna.fischer@hp.com>,
	netdev@vger.kernel.org, bridge@lists.linux-foundation.org,
	linux-kernel@vger.kernel.org,
	virtualization@lists.linux-foundation.org,
	Mark Smith <lk-netdev@lk-netdev.nosense.org>,
	Gerhard Stenzel <gerhard.stenzel@de.ibm.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Jens Osterkamp <jens@linux.vnet.ibm.com>,
	Patrick Mullaney <pmullaney@novell.com>,
	Stephen Hemminger <shemminger@vyatta.com>,
	Edge Virtual Bridging <evb@yahoogroups.com>,
	David Miller <davem@davemloft.net>
Subject: Re: [Bridge] [PATCH 1/4] veth: move loopback logic to common location
Date: Tue, 24 Nov 2009 19:38:28 +0100	[thread overview]
Message-ID: <4B0C2824.5010502@trash.net> (raw)
In-Reply-To: <m1aayb6bfg.fsf@fess.ebiederm.org>

Eric W. Biederman wrote:
> Patrick McHardy <kaber@trash.net> writes:
> 
>> In the layered case (macvlan -> eth0) its common behaviour to
>> keep the mark however. But in case of different namespaces,
>> I think macvlan should also clear the mark on the dev_queue_xmit()
>> path since this is just a shortcut to looping the packets
>> through veth. In fact probably both of them should also clear
>> skb->priority so other namespaces don't accidentally misclassify
>> packets.
> 
> That is why I pushed for what is becoming dev_forward_skb.  So that
> we have one place where we can make all of those tweaks.  It seems
> like in every review we find another field that should be cleared/handled
> specially.
> 
> I don't quite follow what you intend with dev_queue_xmit when the macvlan
> is in one namespace and the real physical device is in another.  Are
> you mentioning that the packet classifier runs in the namespace where
> the primary device lives with packets from a different namespace?

Exactly. And I think we should make sure that the namespace of
the macvlan device can't (deliberately or accidentally) cause
misclassification.

WARNING: multiple messages have this Message-ID (diff)
From: Patrick McHardy <kaber@trash.net>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
	virtualization@lists.linux-foundation.org,
	Herbert Xu <herbert@gondor.apana.org.au>,
	Eric Dumazet <eric.dumazet@gmail.com>,
	Anna Fischer <anna.fischer@hp.com>,
	netdev@vger.kernel.org, bridge@lists.linux-foundation.org,
	linux-kernel@vger.kernel.org,
	Mark Smith <lk-netdev@lk-netdev.nosense.org>,
	Gerhard Stenzel <gerhard.stenzel@de.ibm.com>,
	Jens Osterkamp <jens@linux.vnet.ibm.com>,
	Patrick Mullaney <pmullaney@novell.com>,
	Stephen Hemminger <shemminger@vyatta.com>,
	Edge Virtual Bridging <evb@yahoogroups.com>,
	David Miller <davem@davemloft.net>
Subject: Re: [PATCH 1/4] veth: move loopback logic to common location
Date: Tue, 24 Nov 2009 19:38:28 +0100	[thread overview]
Message-ID: <4B0C2824.5010502@trash.net> (raw)
In-Reply-To: <m1aayb6bfg.fsf@fess.ebiederm.org>

Eric W. Biederman wrote:
> Patrick McHardy <kaber@trash.net> writes:
> 
>> In the layered case (macvlan -> eth0) its common behaviour to
>> keep the mark however. But in case of different namespaces,
>> I think macvlan should also clear the mark on the dev_queue_xmit()
>> path since this is just a shortcut to looping the packets
>> through veth. In fact probably both of them should also clear
>> skb->priority so other namespaces don't accidentally misclassify
>> packets.
> 
> That is why I pushed for what is becoming dev_forward_skb.  So that
> we have one place where we can make all of those tweaks.  It seems
> like in every review we find another field that should be cleared/handled
> specially.
> 
> I don't quite follow what you intend with dev_queue_xmit when the macvlan
> is in one namespace and the real physical device is in another.  Are
> you mentioning that the packet classifier runs in the namespace where
> the primary device lives with packets from a different namespace?

Exactly. And I think we should make sure that the namespace of
the macvlan device can't (deliberately or accidentally) cause
misclassification.

  parent reply	other threads:[~2009-11-24 18:38 UTC|newest]

Thread overview: 90+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-24  0:56 [Bridge] [PATCHv2 0/4] macvlan: add vepa and bridge mode Arnd Bergmann
2009-11-24  0:56 ` Arnd Bergmann
2009-11-24  0:56 ` [Bridge] [PATCH 1/4] veth: move loopback logic to common location Arnd Bergmann
2009-11-24  0:56   ` Arnd Bergmann
2009-11-24  9:51   ` Patrick McHardy
2009-11-24  9:51   ` [Bridge] " Patrick McHardy
2009-11-24  9:51     ` Patrick McHardy
2009-11-24 10:02     ` Arnd Bergmann
2009-11-24 10:02     ` [Bridge] " Arnd Bergmann
2009-11-24 10:02       ` Arnd Bergmann
2009-11-24 10:17       ` Patrick McHardy
2009-11-24 10:17       ` [Bridge] " Patrick McHardy
2009-11-24 10:17         ` Patrick McHardy
2009-11-24 10:34         ` [Bridge] " Arnd Bergmann
2009-11-24 10:34           ` Arnd Bergmann
2009-11-24 10:40           ` [Bridge] " Patrick McHardy
2009-11-24 10:40             ` Patrick McHardy
2009-11-24 13:13             ` [Bridge] " Arnd Bergmann
2009-11-24 13:13               ` Arnd Bergmann
2009-11-24 13:13             ` Arnd Bergmann
2009-11-24 16:42             ` Eric W. Biederman
2009-11-24 16:42             ` [Bridge] " Eric W. Biederman
2009-11-24 16:42               ` Eric W. Biederman
2009-11-24 16:56               ` Patrick McHardy
2009-11-24 16:56               ` [Bridge] " Patrick McHardy
2009-11-24 16:56                 ` Patrick McHardy
2009-11-24 18:10                 ` Eric W. Biederman
2009-11-24 18:10                 ` [Bridge] " Eric W. Biederman
2009-11-24 18:10                   ` Eric W. Biederman
2009-11-24 18:28                   ` Arnd Bergmann
2009-11-24 18:28                   ` [Bridge] " Arnd Bergmann
2009-11-24 18:28                     ` Arnd Bergmann
2009-11-24 18:38                   ` Patrick McHardy [this message]
2009-11-24 18:38                     ` Patrick McHardy
2009-11-26 15:21                     ` [Bridge] " Arnd Bergmann
2009-11-26 15:21                       ` Arnd Bergmann
2009-11-26 15:33                       ` [Bridge] " Patrick McHardy
2009-11-26 15:33                         ` Patrick McHardy
2009-11-26 16:38                         ` [Bridge] " Eric W. Biederman
2009-11-26 16:38                           ` Eric W. Biederman
2009-11-26 16:38                         ` Eric W. Biederman
2009-11-26 17:44                         ` Arnd Bergmann
2009-11-26 17:44                         ` [Bridge] " Arnd Bergmann
2009-11-26 17:44                           ` Arnd Bergmann
2009-11-26 21:14                           ` Patrick McHardy
2009-11-26 21:14                           ` [Bridge] " Patrick McHardy
2009-11-26 21:14                             ` Patrick McHardy
2009-11-26 15:33                       ` Patrick McHardy
2009-11-26 15:21                     ` Arnd Bergmann
2009-11-24 18:38                   ` Patrick McHardy
2009-11-24 10:40           ` Patrick McHardy
2009-11-24 10:34         ` Arnd Bergmann
2009-11-24  0:56 ` Arnd Bergmann
2009-11-24  0:56 ` [PATCH 2/4] macvlan: cleanup rx statistics Arnd Bergmann
2009-11-24  0:56 ` [Bridge] " Arnd Bergmann
2009-11-24  0:56   ` Arnd Bergmann
2009-11-24  8:15   ` Eric Dumazet
2009-11-24  8:15   ` [Bridge] " Eric Dumazet
2009-11-24  8:15     ` Eric Dumazet
2009-11-24  8:45     ` Arnd Bergmann
2009-11-24  8:45     ` [Bridge] " Arnd Bergmann
2009-11-24  8:45       ` Arnd Bergmann
2009-11-24  9:28       ` Arnd Bergmann
2009-11-24  9:28       ` [Bridge] " Arnd Bergmann
2009-11-24  9:28         ` Arnd Bergmann
2009-11-24 10:41   ` Patrick McHardy
2009-11-24 10:41   ` [Bridge] " Patrick McHardy
2009-11-24 10:41     ` Patrick McHardy
2009-11-24  0:56 ` [Bridge] [PATCH 3/4] macvlan: implement bridge, VEPA and private mode Arnd Bergmann
2009-11-24  0:56   ` Arnd Bergmann
2009-11-24  0:56   ` Arnd Bergmann
2009-11-24  0:56   ` Arnd Bergmann
2009-11-24 10:42   ` Patrick McHardy
2009-11-24 10:42   ` [Bridge] " Patrick McHardy
2009-11-24 10:42     ` Patrick McHardy
2009-11-24 12:45     ` Arnd Bergmann
2009-11-24 12:45     ` [Bridge] " Arnd Bergmann
2009-11-24 12:45       ` Arnd Bergmann
2009-11-24  0:56 ` [PATCH 4/4] macvlan: export macvlan mode through netlink Arnd Bergmann
2009-11-24  0:56 ` [Bridge] " Arnd Bergmann
2009-11-24  0:56   ` Arnd Bergmann
2009-11-24 10:53   ` [Bridge] " Patrick McHardy
2009-11-24 10:53     ` Patrick McHardy
2009-11-24 12:57     ` Arnd Bergmann
2009-11-24 12:57     ` [Bridge] " Arnd Bergmann
2009-11-24 12:57       ` Arnd Bergmann
2009-11-24 13:47       ` Patrick McHardy
2009-11-24 13:47       ` [Bridge] " Patrick McHardy
2009-11-24 13:47         ` Patrick McHardy
2009-11-24 10:53   ` Patrick McHardy

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=4B0C2824.5010502@trash.net \
    --to=kaber@trash.net \
    --cc=anna.fischer@hp.com \
    --cc=arnd@arndb.de \
    --cc=bridge@lists.linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=ebiederm@xmission.com \
    --cc=eric.dumazet@gmail.com \
    --cc=evb@yahoogroups.com \
    --cc=gerhard.stenzel@de.ibm.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=jens@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lk-netdev@lk-netdev.nosense.org \
    --cc=netdev@vger.kernel.org \
    --cc=pmullaney@novell.com \
    --cc=shemminger@vyatta.com \
    --cc=virtualization@lists.linux-foundation.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.