netdev - Re: [PATCH iproute2-next] erspan: Add type I version 0 support.

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] [day] [month] [year] [list]

Date:   Wed, 29 Apr 2020 20:40:18 -0600
From:   David Ahern <dsahern@...il.com>
To:     William Tu <u9012063@...il.com>
Cc:     Linux Kernel Network Developers <netdev@...r.kernel.org>,
        Petr Machata <petrm@...lanox.com>,
        Xin Long <lucien.xin@...il.com>, guy@...m.mit.edu,
        Dmitriy Andreyevskiy <dandreye@...co.com>
Subject: Re: [PATCH iproute2-next] erspan: Add type I version 0 support.

On 4/29/20 6:45 PM, William Tu wrote:
> On Wed, Apr 29, 2020 at 2:52 PM David Ahern <dsahern@...il.com> wrote:
>>
>> On 4/26/20 9:04 AM, William Tu wrote:
>>> The Type I ERSPAN frame format is based on the barebones
>>> IP + GRE(4-byte) encapsulation on top of the raw mirrored frame.
>>> Both type I and II use 0x88BE as protocol type. Unlike type II
>>> and III, no sequence number or key is required.
>>
>> should this be considered a bug fix or -next is what you prefer?
>>
> Hi David,
> Since it's supporting a new type, I'd consider -next.
> But either way is ok to me, I don't have have any preference.
> Thanks!
> William
> 

applied to iproute2-next.