netdev - Re: [RFC v2 PATCH 4/5] seg6: Add sysctl limits for segment routing header

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]

Message-ID: <673e5177-eaa2-9b5f-f750-4e5106eda5ea@gmail.com>
Date:   Sat, 8 Jun 2019 11:24:16 +0100
From:   David Lebrun <dav.lebrun@...il.com>
To:     Tom Herbert <tom@...bertland.com>, davem@...emloft.net,
        netdev@...r.kernel.org, dlebrun@...gle.com
Cc:     Tom Herbert <tom@...ntonium.net>
Subject: Re: [RFC v2 PATCH 4/5] seg6: Add sysctl limits for segment routing
 header

On 07/06/2019 19:55, Tom Herbert wrote:
> +		.procname	= "max_srh_tlvs_length",

Should this be "max_srh_opts_length" to be consistent with the rest of 
the naming ?