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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200923.120243.174960615983472672.davem@davemloft.net>
Date:   Wed, 23 Sep 2020 12:02:43 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     dsahern@...il.com
Cc:     eric.dumazet@...il.com, zenczykowski@...il.com, maze@...gle.com,
        netdev@...r.kernel.org, willemb@...gle.com, lorenzo@...gle.com,
        sgill@...cinc.com, vparadka@....qualcomm.com, twear@...cinc.com,
        dsahern@...nel.org
Subject: Re: [PATCH v2] net/ipv4: always honour route mtu during forwarding

From: David Ahern <dsahern@...il.com>
Date: Wed, 23 Sep 2020 08:36:50 -0600

> On 9/23/20 2:46 AM, Eric Dumazet wrote:
>> Apparently route mtu are capped to 65520, not sure where it is done exactly IP_MAX_MTU being 65535)
> 
> ip_metrics_convert seems to be the place"
>                 if (type == RTAX_MTU && val > 65535 - 15)
>                         val = 65535 - 15;
> 
> going back through the code moves, and it was added by Dave with
> 710ab6c03122c

At the time of that commit IP_MAX_MTU only existed in net/ipv4/route.c
and it's value was 0xFFF0.

So I didn't add anything :-)  Just moving stuff around.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ