summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (from: 45fd9ca)
raw | patch | inline | side by side (from: 45fd9ca)
author | Buddy Liong <buddy.budiono@ti.com> | |
Tue, 19 May 2015 14:11:23 +0000 (09:11 -0500) | ||
committer | Angela Stegmaier <angelabaker@ti.com> | |
Thu, 17 Sep 2015 19:15:43 +0000 (14:15 -0500) |
During the recovery, in deinit_ipc(), the IPC resource manager will
try to dump the remote core trace information to a file. There is a
possibility that the trace buffer may have become corrupted as a result
of the crash on the remote core and that the write index, which resides
in the trace buffer, has become corrupted as well. In this situation,
there is a potential that the trace dump code will read beyond the mapped
buffer for the TRACE BUF memory, causing the system to crash and be
unable to recover. At this point a system restart is required to
recover the system.
There should be a check to make sure that the trace dump code is not
indexing beyond the end of the trace buffer.
Signed-off-by: Buddy Liong <buddy.budiono@ti.com>
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
try to dump the remote core trace information to a file. There is a
possibility that the trace buffer may have become corrupted as a result
of the crash on the remote core and that the write index, which resides
in the trace buffer, has become corrupted as well. In this situation,
there is a potential that the trace dump code will read beyond the mapped
buffer for the TRACE BUF memory, causing the system to crash and be
unable to recover. At this point a system restart is required to
recover the system.
There should be a check to make sure that the trace dump code is not
indexing beyond the end of the trace buffer.
Signed-off-by: Buddy Liong <buddy.budiono@ti.com>
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
No differences found