| commit | 98f830cdfc8258fb36fc856bef80d25ddedf5c31 | |
| author | Volker Lendecke <vl@samba.org> | |
| Thu, 25 Dec 2008 12:44:11 +0000 (25 13:44 +0100) | ||
| committer | Volker Lendecke <vl@samba.org> | |
| Wed, 31 Dec 2008 18:33:25 +0000 (31 19:33 +0100) | ||
| tree | a5d2fffbbf2a79ffeed0baff6da99b91d4f2298f | treesnapshot (tar.gz zip) |
| parent | e0fd61f0cbfb0a25c8e9603375c2eb98936c8345 | commitdiff |
Disable the use of splice(2)
On a debian lenny installation with a kernel that calls itself 2.6.28, I could
repeatably block smbd using splice. According to the output of netstat, the
recvq of the TCP connection was full and at the same time according to strace
smbd was stuck in a splice syscall trying to read from that TCP connection. We
can not protect ourselves from this condition, as nobody will ever notify us
that something is broken. So sadly we can't use splice yet at all. Maybe in
2.6.29...
On a debian lenny installation with a kernel that calls itself 2.6.28, I could
repeatably block smbd using splice. According to the output of netstat, the
recvq of the TCP connection was full and at the same time according to strace
smbd was stuck in a splice syscall trying to read from that TCP connection. We
can not protect ourselves from this condition, as nobody will ever notify us
that something is broken. So sadly we can't use splice yet at all. Maybe in
2.6.29...
| source3/lib/recvfile.c | diffblobblamehistory |