From: Patrick McHardy <kaber@trash.net>
To: Arnd Bergmann <arnd@arndb.de>
Cc: David Miller <davem@davemloft.net>,
"Eric W. Biederman" <ebiederm@xmission.com>,
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>
Subject: Re: [PATCH 1/4] veth: move loopback logic to common location
Date: Thu, 26 Nov 2009 22:14:25 +0100 [thread overview]
Message-ID: <4B0EEFB1.3080403@trash.net> (raw)
In-Reply-To: <200911261844.59912.arnd@arndb.de>
Arnd Bergmann wrote:
> On Thursday 26 November 2009, Patrick McHardy wrote:
>> In addition to those already handled, I'd say
>>
>> - priority: affects qdisc classification, may refer to classes of the
>> old namespace
>> - ipvs_property: might cause packets to incorrectly skip netfilter hooks
>> - nf_trace: might trigger packet tracing
>> - nf_bridge: contains references to network devices in the old NS,
>> also indicates packet was bridged
>> - iif: index is only valid in the originating namespace
>> - probably secmark.
>
> ok
>
>> - tc_index: classification result, should only be set in the namespace
>> of the classifier
>> - tc_verd: RTTL etc. should begin at zero again
>
> Wouldn't that defeat the purpose of RTTL? If you create a loop
> across two devices in different namespaces, it may no longer get
> detected. Or is that a different problem again?
Mhh good point, that would indeed be possible. OTOH using ingress
filtering in one namespace currently might cause the packet to get
dropped in a different namespace because the ttl runs out. For now
I'd suggest to go the safe route and keep the TTL intact until we
can come up with something better.
> +void skb_set_dev(struct sk_buff *skb, struct net_device *dev)
> +{
> + if (skb->dev && !net_eq(dev_net(skb->dev), dev_net(dev))) {
> + secpath_reset(skb);
> + skb_dst_drop(skb);
> + nf_reset(skb);
> + skb_init_secmark(skb);
> + skb->mark = 0;
> + skb->priority = 0;
> + skb->nf_trace = 0;
> + skb->ipvs_property = 0;
> +#ifdef CONFIG_NET_SCHED
> + skb->tc_index = 0;
> +#ifdef CONFIG_NET_CLS_ACT
> + skb->tc_verd = SET_TC_VERD(skb->tc_verd, 0);
> + skb->tc_verd = SET_TC_RTTL(skb->tc_verd, 0);
> +#endif
> +#endif
This makes we wonder which ones we actually should keep. Most of the
others get reinitialized anyways, so maybe its better to simply clear
the entire area up until ->tail like f.i. skb_recycle_check().
> + }
> + skb->dev = dev;
> + skb->skb_iif = skb->dev->ifindex;
This doesn't seem necessary, if the packet goes through
netif_receive_skb, it will be set anyways.
> +}
> +EXPORT_SYMBOL(skb_set_dev);
next prev parent reply other threads:[~2009-11-26 21:14 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-24 0:56 [PATCHv2 0/4] macvlan: add vepa and bridge mode Arnd Bergmann
2009-11-24 0:56 ` [PATCH 1/4] veth: move loopback logic to common location Arnd Bergmann
2009-11-24 9:51 ` Patrick McHardy
2009-11-24 10:02 ` Arnd Bergmann
2009-11-24 10:17 ` Patrick McHardy
2009-11-24 10:34 ` Arnd Bergmann
2009-11-24 10:40 ` Patrick McHardy
2009-11-24 13:13 ` Arnd Bergmann
2009-11-24 16:42 ` Eric W. Biederman
2009-11-24 16:56 ` Patrick McHardy
2009-11-24 18:10 ` Eric W. Biederman
2009-11-24 18:28 ` Arnd Bergmann
2009-11-24 18:38 ` Patrick McHardy
2009-11-26 15:21 ` Arnd Bergmann
2009-11-26 15:33 ` Patrick McHardy
2009-11-26 16:38 ` Eric W. Biederman
2009-11-26 17:44 ` Arnd Bergmann
2009-11-26 21:14 ` Patrick McHardy [this message]
2009-11-24 0:56 ` [PATCH 2/4] macvlan: cleanup rx statistics Arnd Bergmann
2009-11-24 8:15 ` Eric Dumazet
2009-11-24 8:45 ` Arnd Bergmann
2009-11-24 9:28 ` Arnd Bergmann
2009-11-24 10:41 ` Patrick McHardy
2009-11-24 0:56 ` [PATCH 3/4] macvlan: implement bridge, VEPA and private mode Arnd Bergmann
2009-11-24 10:42 ` Patrick McHardy
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 10:53 ` Patrick McHardy
2009-11-24 12:57 ` Arnd Bergmann
2009-11-24 13:47 ` 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=4B0EEFB1.3080403@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=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 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).