netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steffen Klassert <steffen.klassert@secunet.com>
To: Benedict Wong <benedictwong@google.com>
Cc: <netdev@vger.kernel.org>, <nharold@google.com>,
	<lorenzo@google.com>, <maze@google.com>
Subject: Re: [PATCH ipsec, resend 0/1] xfrm: set-mark default behavior changes
Date: Sat, 12 Jan 2019 11:01:58 +0100	[thread overview]
Message-ID: <20190112100158.GE8742@gauss3.secunet.de> (raw)
In-Reply-To: <20190111201412.176246-1-benedictwong@google.com>

On Fri, Jan 11, 2019 at 12:14:11PM -0800, Benedict Wong wrote:
> A behavior change introduced in 9b42c1f179a6 (“xfrm: Extend the
> output_mark to support input direction and masking”) results in a
> change in:
> 
> 1. Default outbound behavior with regards to route lookup marks, and
> 2. Inbound behavior for SAs used to decapsulate packets when the output
>      mark (as specified in 4.14 to 4.18) is set.
> 
> This patch set restores the previous default outbound behavior,
> resolving (1), but behavior change (2) will require more discussion.
> 
> Specifically, in (2), a SA with a "output mark" set will now have that
> Mark imposed on the inbound packet (As opposed to the previous
> output-mark behavior where the inbound packet's mark would not be
> touched). This is less of a concern, as it is limited to the case where:
> 
> 1. SA output mark is set
> 2. SA is using non-transport mode
> 3. SA is configured for inbound decapsulation (local dst IP)
> 
> Critically, conditions 1 and 3 imply a configuration that output mark
> was not designed to support. The only valid use case for this seems
> to be the loopback case (as IP addresses would apply bidirectionally).
> As such, we believe that this behavioral change is acceptable as is.

There was no need to resend this without changes. I still had this
patchset in my queue. I'm ok with the change, but you did not Cc
all the authors of the patch you want to fix. So please resend once
again with Cc to all the authors, so that they have a chance to
review this change.

Thanks!

  parent reply	other threads:[~2019-01-12 10:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-11 20:14 [PATCH ipsec, resend 0/1] xfrm: set-mark default behavior changes Benedict Wong
2019-01-11 20:14 ` [PATCH ipsec, resend 1/1] xfrm: Make set-mark default behavior backward compatible Benedict Wong
2019-01-12 10:01 ` Steffen Klassert [this message]
2019-01-14 18:29   ` [PATCH ipsec, resend 0/1] xfrm: set-mark default behavior changes Benedict Wong
  -- strict thread matches above, loose matches on Subject: below --
2019-01-14 19:24 Benedict Wong

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=20190112100158.GE8742@gauss3.secunet.de \
    --to=steffen.klassert@secunet.com \
    --cc=benedictwong@google.com \
    --cc=lorenzo@google.com \
    --cc=maze@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=nharold@google.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 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).