netdev - Re: [PATCH iproute2-next] ip xfrm: support setting/printing XFRMA_IF

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 5 Apr 2019 09:59:51 +0300
From:   Eyal Birger <eyal.birger@...il.com>
To:     Stephen Hemminger <stephen@...workplumber.org>
Cc:     netdev@...r.kernel.org, antony@...nome.org
Subject: Re: [PATCH iproute2-next] ip xfrm: support setting/printing
 XFRMA_IF_ID attribute in states/policies

Hi Stephen,

On Thu, 4 Apr 2019 10:13:36 -0700
Stephen Hemminger <stephen@...workplumber.org> wrote:

> On Thu,  4 Apr 2019 19:07:38 +0300
> Eyal Birger <eyal.birger@...il.com> wrote:
> 
> > The XFRMA_IF_ID attribute is set in policies/states for them to be
> > associated with an XFRM interface (4.19+).
> > 
> > Add support for setting / displaying this attribute.
> > 
> > Note that 0 is a valid value therefore set XFRMA_IF_ID if any value
> > was provided in command line.
> > 
> > Tested-by: Antony Antony <antony@...nome.org>
> > Signed-off-by: Eyal Birger <eyal.birger@...il.com>
> > ---  
> 
> Since this works with existing kernel int should not need to wait for
> next.

Oh, sorry about that.

The patch applies cleanly and works on the iproute2 tree. Should I
resubmit?

Thanks!
Eyal.