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