aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/s390/s390dbf.txt
diff options
context:
space:
mode:
authorHeiko Carstens <heiko.carstens@de.ibm.com>2009-09-11 10:28:58 +0200
committerMartin Schwidefsky <schwidefsky@de.ibm.com>2009-09-11 10:29:53 +0200
commit0c88ee5b7523e76e290d558c28cd0be48ffad597 (patch)
treec603735c1012c231a4cc2d315bb30f795e1c4781 /Documentation/s390/s390dbf.txt
parent50aa98bad056a17655864a4d71ebc32d95c629a7 (diff)
downloadmrst-s0i3-test-0c88ee5b7523e76e290d558c28cd0be48ffad597.tar.gz
mrst-s0i3-test-0c88ee5b7523e76e290d558c28cd0be48ffad597.tar.xz
mrst-s0i3-test-0c88ee5b7523e76e290d558c28cd0be48ffad597.zip
[S390] Initialize __LC_THREAD_INFO early.
"lockdep: Fix backtraces" reveales a bug in early setup code: when lockdep tries to save a stack backtrace before setup_arch has been called the lowcore pointer for the current thread info pointer isn't initialized yet. However our save stack backtrace code relies on it. If the pointer isn't initialized the saved backtrace will have zero entries. lockdep however relies (correctly) on the fact that that cannot happen. A write access to some random memory region is the result. Fix this by initializing the thread info pointer early. Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com> Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
Diffstat (limited to 'Documentation/s390/s390dbf.txt')
0 files changed, 0 insertions, 0 deletions