netdev - Re: [PATCHv2 net-next 0/2] gre: add sequence number for collect md mode.

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]

Message-Id: <20180304.183521.2055620354660523937.davem@davemloft.net>
Date:   Sun, 04 Mar 2018 18:35:21 -0500 (EST)
From:   David Miller <davem@...emloft.net>
To:     u9012063@...il.com
Cc:     netdev@...r.kernel.org, daniel@...earbox.net, ast@...nel.org
Subject: Re: [PATCHv2 net-next 0/2] gre: add sequence number for collect md
 mode.

From: William Tu <u9012063@...il.com>
Date: Thu,  1 Mar 2018 13:49:56 -0800

> Currently GRE sequence number can only be used in native tunnel mode.
> The first patch adds sequence number support for gre collect
> metadata mode, and the second patch tests it using BPF.
> 
> RFC2890 defines GRE sequence number to be specific to the traffic
> flow identified by the key.  However, this patch does not implement
> per-key seqno.  The sequence number is shared in the same tunnel
> device. That is, different tunnel keys using the same collect_md
> tunnel share single sequence number.
> 
> A new BFP uapi tunnel flag 'BPF_F_SEQ_NUMBER' is added.
> --
> v1->v2:
>   rename BPF_F_GRE_SEQ to BPF_F_SEQ_NUMBER suggested by Daniel

Series applied, thank you.