netdev - Re: [PATCH] net: make tc-police action MTU behavior match documentation

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: <CAM_iQpU2aVsD=kG+B8--VbahQftCwA-c9KPun1MwwwRHO=jVEA@mail.gmail.com>
Date:   Mon, 26 Feb 2018 19:45:30 -0800
From:   Cong Wang <xiyou.wangcong@...il.com>
To:     Andrew Collins <acollins@...dlepoint.com>
Cc:     Jamal Hadi Salim <jhs@...atatu.com>,
        David Miller <davem@...emloft.net>,
        Linux Kernel Network Developers <netdev@...r.kernel.org>
Subject: Re: [PATCH] net: make tc-police action MTU behavior match documentation

On Mon, Feb 26, 2018 at 12:10 PM, Andrew Collins
<acollins@...dlepoint.com> wrote:
> The man page for tc-police states that the MTU defaults to
> unlimited if peakrate is not specified, but it actually defaults
> to 2047.

I don't find such statement from the man page:
http://man7.org/linux/man-pages/man8/tc-police.8.html


What am I missing?