https://bugs.winehq.org/show_bug.cgi?id=35781
--- Comment #12 from Austin English austinenglish@gmail.com --- (In reply to Austin English from comment #11)
Kernel bug is at https://bugzilla.kernel.org/show_bug.cgi?id=73811
From upstream:
=== Hm, I really don't see through this whole Windows style source code. :(
Is it possible that you could demonstrate the problem in a very simple and as minimal as possible stand-alone C program? That would be great.
This change only affects memory accounting, and says that the minimum sizes for that are SOCK_MIN_SNDBUF resp. SOCK_MIN_RCVBUF, so it simply clamps the limits slightly.
Perhaps you do a setsockopt() somewhere in wine code and account for memory additionally in user space? So that your assumptions about the actual available memory in kernel space are not correct anymore?
Thanks,
Daniel ===
if someone has/can make a testcase, I'll forward it upstream.