netdev - Re: [PATCH RFC net-next 00/11] udp gso

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: <20180419.134512.2236555560549522651.davem@davemloft.net>
Date:   Thu, 19 Apr 2018 13:45:12 -0400 (EDT)
From:   David Miller <davem@...emloft.net>
To:     willemdebruijn.kernel@...il.com
Cc:     netdev@...r.kernel.org, willemb@...gle.com
Subject: Re: [PATCH RFC net-next 00/11] udp gso

From: Willem de Bruijn <willemdebruijn.kernel@...il.com>
Date: Wed, 18 Apr 2018 14:12:40 -0400

> Actually, yes, I should be able to relax that constraint with
> segmentation.
> 
> It is there in case a corked packet may grow to the point of
> having to be fragmented. But segmentation already ensures
> that its datagrams always fit in MTU.
> 
> Should be simple refinement to
> 
>             !(flags & MSG_MORE) &&
> 
> in __ip_append_data.

Right, if segmentation never sends greater than mtu then we can
relax the restriction in this way.

Great idea.