On Tue, Jan 12, 2021 at 9:43 PM Heath Caldwell [off-list ref] wrote:
On 2021-01-12 21:26 (+0100), Eric Dumazet [off-list ref] wrote:
quoted
This is fine. This has been done forever. Your change might break applications.
In what way might applications be broken?
It seems to be a very strange position to allow a configured maximum to
be violated because of obscure precedent.
Welcome to the real world
Some applications use setsockopt(), followed by getsockopt() to make
sure their change has been recorded.
Some setups might break, you can be sure of this.
I doubt this issue is serious enough, the code has been there forever.
Please fix the documentation (if any)