From: Nicolas Dichtel <nicolas.dichtel@6wind•com>
To: Mahesh Bandewar <maheshb@google•com>, David Miller <davem@davemloft•net>
Cc: mahesh@bandewar•net, Eric Dumazet <edumazet@google•com>,
linux-netdev <netdev@vger•kernel.org>
Subject: Re: [PATCH next v2 0/7] Introduce l3_dev pointer for L3 processing
Date: Thu, 17 Mar 2016 09:47:47 +0100 [thread overview]
Message-ID: <56EA6F33.6050603@6wind.com> (raw)
In-Reply-To: <CAF2d9jgqAqUxN0HSTUguQyf6m62wDWizTH4bQ+Hz1xxte-=kaQ@mail.gmail.com>
Le 14/03/2016 18:57, Mahesh Bandewar a écrit :
> On Sun, Mar 13, 2016 at 8:53 PM, David Miller <davem@davemloft•net> wrote:
[snip]
>> Furthermore, when you walk across the ns boundary, that old device has
>> to disappear. That's why that is the device assigned to skb->dev.
>>
> The layer boundaries are not that well maintained. We do check for the xfrm
> policies in L4 and expect the skb->dev pointing to the L3 device. So unless we
> have a way to derive a L3 dev from skb->dev, I don't think xfrm will
> work. Unless
> some Xfrm-expert asserts that this is not needed.
Adding a hook "at the right place" to do the switch is probably the better way.
For xfrm, you will need to handle it in this hook or rearrange things.
I don't think that a quick and easy solution will be possible.
next prev parent reply other threads:[~2016-03-17 8:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 21:49 [PATCH next v2 0/7] Introduce l3_dev pointer for L3 processing Mahesh Bandewar
2016-03-10 9:47 ` Nicolas Dichtel
2016-03-10 21:29 ` Cong Wang
2016-03-14 0:01 ` Mahesh Bandewar
2016-03-14 18:13 ` Cong Wang
2016-03-13 23:44 ` Mahesh Bandewar
2016-03-14 1:50 ` David Miller
2016-03-14 2:29 ` Mahesh Bandewar
2016-03-14 3:53 ` David Miller
2016-03-14 17:57 ` Mahesh Bandewar
2016-03-17 8:47 ` Nicolas Dichtel [this message]
2016-03-14 18:15 ` Cong Wang
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=56EA6F33.6050603@6wind.com \
--to=nicolas.dichtel@6wind$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=mahesh@bandewar$(echo .)net \
--cc=maheshb@google$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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