| 1 |
My Tor node gets killed once every day or two with the following message in |
| 2 |
dmesg: |
| 3 |
|
| 4 |
PAX: size overflow detected in function tcp_recvmsg net/ipv4/tcp.c:1696 |
| 5 |
Pid: 28327, comm: tor Not tainted 3.4.4-hardened-r1 #1 |
| 6 |
Call Trace: |
| 7 |
[<ffffffff8112813b>] report_size_overflow+0x34/0x3e |
| 8 |
[<ffffffff8154b573>] tcp_recvmsg+0x5fa/0x8ca |
| 9 |
[<ffffffff81567bde>] inet_recvmsg+0x69/0x83 |
| 10 |
[<ffffffff814f6ca3>] sock_aio_read.part.21+0x104/0x11c |
| 11 |
[<ffffffff814f6d01>] sock_aio_read+0x46/0x51 |
| 12 |
[<ffffffff8112072a>] do_sync_read+0xda/0x122 |
| 13 |
[<ffffffff81036b68>] ? __switch_to+0x1af/0x382 |
| 14 |
[<ffffffff81092835>] ? finish_task_switch+0xb6/0xc5 |
| 15 |
[<ffffffff811210ec>] vfs_read+0x140/0x1a5 |
| 16 |
[<ffffffff8112143b>] sys_read+0x50/0x78 |
| 17 |
[<ffffffff81610a5c>] system_call_fastpath+0x1c/0x21 |
| 18 |
|
| 19 |
Is there a way to figure out where Tor goes wrong and provokes this error? No |
| 20 |
core dump is produced, and not even running Tor under GDB helps - execution |
| 21 |
ends with: |
| 22 |
|
| 23 |
Program terminated with signal SIGKILL, Killed. |
| 24 |
The program no longer exists. |
| 25 |
|
| 26 |
-- |
| 27 |
Karl-Johan Karlsson |
Archives