mptcp

Yeah, this is the real problem. To be clear though (the article skimmed over lots of details to remain generally accessible), I was not discussing the release_sock() function which releases a lock on a socket [1]. Instead, my code registers a set of function pointers in a struct [2]. While release_sock() does have documentation, the function pointer of the same name does not, and the only examples I have are other files of code within the MPTCP protocol implementation. The callback is related to the function, to be sure, and so I should have connected the dots, but this is how we learn. While I was making a baseless assumption, I like to believe that it was baseless because there was not enough available information, and not because I was ignoring obvious sources of information :P [1]: http://lxr.free-electrons.com/ident?v=4.1;i=release_s

When they say that, they mean in their fork of the Linux kernel: https://github.com/multipath-tcp/mptcp not in the official upstream kernel from Linus https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.... nor any of the mainstream distro kernels. You can check this for yourself. Just take a look for the MPTCP patches in Linus's kernel. You won't find them. Here's my kernel git repo; origin is Linus's repo, mptcp is the MPTCP development repo: $ git log --pretty=oneline origin/master..mptcp/mptcp_v0.87 | wc -l 2841 As you can see, there are 2841 patches in the mptcp_v0.87 branch that are not in the kernel repo, all the way back to the original shim6 patch that was used to start building MPTCP on top of shim6, which was a proposal for multi-homed IPv6 (MPTCP now works on top of IPv4 as well). Note that when you look at t