Skip to main content

Browse the archive

Revision 5f630401f9e98bd062733b5bbef096dbf2158066 authored by Tiejun Chen on 22 August 2012, 16:10:20 UTC, committed by Benjamin Herrenschmidt on 24 August 2012, 10:26:06 UTC 
powerpc/kgdb: Restore current_thread_info properly
 
For powerpc BooKE and e200, singlestep is handled on the critical/dbg
exception stack. This causes current_thread_info() to fail for kgdb
internal, so previously We work around this issue by copying
the thread_info from the kernel stack before calling kgdb_handle_exception,
and copying it back afterwards.

But actually we don't do this properly. We should backup current_thread_info
then restore that when exit.

Signed-off-by: Tiejun Chen <tiejun.chen@windriver.com>
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
1 parent 949616c
Raw File
BUGS 
- Out-of-space may cause a severe problem if the object (and directory entry)
  were written, but the inode attributes failed. Then if the filesystem was
  unmounted and mounted the kernel can get into an endless loop doing a readdir.
back to top