Part Number:TCI6630K2L
Tool/software: Linux
The IPC server program /usr/bin/lad_tci6630 generates a log file /tmp/LAD/lad.txt. Under easily replicated circumstances, this program sends huge number of messages to /tmp/LAD/lad.txt, and can fill up the /tmp disk in a matter of minutes.
After about 15 seconds:
wc -l lad.txt
1546901 lad.txt
ls -l lad.txt
-rw-r--r-- 1 root root 94821091 Mar 26 16:13 lad.txt
high-level way to reproduce:
1 - run a DSP program that uses the ipc manager and creates a local mqueue.
2 - run an arm linux program that does an mqueue open.
3 - stop the DSP program: mpmcl reset dsp0
Here is the text that repeats infinitely many times:
[660.935608] Socket is no longer valid, MUST re-attach!
[660.935614] NameServer_reattach: --> procId=1, refCount=1
[660.935627] NameServer_reattach: created send socket: 2, procId 1
[660.935637] NameServer_reattach: connect failed: procId=1, errno=22 (Invalid argument)
[660.935646] closing send socket: 2
[660.935661] NameServer_reattach: <-- refCount=1, status=-1
[660.935669] NameServer: waiting for unblockFd: 1, and socks: maxfd: 7
[660.935680] NameServer: back from select()
[660.935686] NameServer: Listener got NameServer message from sock: 7!
[660.935694] recvfrom failed: Link has been severed (67)
[660.935702] Socket is no longer valid, MUST re-attach!
[660.935708] NameServer_reattach: --> procId=1, refCount=1
From the timestamp, you can see that this block of messages is sent to /tmp/lad.txt about 10,000 times per second.
Greg Johnson