netdev - Re: [PATCH net-next] ipv4: Namespecify TCP PMTU mechanism

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: <20150209.140911.1096080668059319311.davem@redhat.com>
Date:	Mon, 09 Feb 2015 14:09:11 -0800 (PST)
From:	David Miller <davem@...hat.com>
To:	fan.du@...el.com
Cc:	jheffner@....edu, netdev@...r.kernel.org,
	fengyuleidian0615@...il.com
Subject: Re: [PATCH net-next] ipv4: Namespecify TCP PMTU mechanism

From: Fan Du <fan.du@...el.com>
Date: Mon,  9 Feb 2015 16:44:58 +0800

> Packetization Layer Path MTU Discovery works separately beside
> Path MTU Discovery at IP level, different net namespace has
> various requirements on which one to chose, e.g., a virutalized
> container instance would require TCP PMTU to probe an usable
> effective mtu for underlying tunnel, while the host would
> employ classical ICMP based pmtu to function.
> 
> Hence making TCP PMTU mechanism per net namespace to decouple
> two functionality. Furthermore the probe base MSS should also
> be configured separately for each namespace.
> 
> Signed-off-by: Fan Du <fan.du@...el.com>

This does not apply cleanly to net-next, please respin.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html