netdev - Re: [PATCH] Revert "ipv6: add mtu lock check in __ip6_rt_update

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]

Date:   Tue, 05 May 2020 14:23:22 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     zenczykowski@...il.com
Cc:     maze@...gle.com, netdev@...r.kernel.org, edumazet@...gle.com,
        willemb@...gle.com, lucien.xin@...il.com,
        hannes@...essinduktion.org
Subject: Re: [PATCH] Revert "ipv6: add mtu lock check in
 __ip6_rt_update_pmtu"

From: Maciej Żenczykowski <zenczykowski@...il.com>
Date: Tue,  5 May 2020 11:57:23 -0700

> The above reasoning is incorrect.  IPv6 *requires* icmp based pmtu to work.
> There's already a comment to this effect elsewhere in the kernel:

How can an internet standard specify a system local policy decision
on this level?

If I want to lock the MTU value on my ipv6 routes, I have a reason
and I should be able to do it.