| commit | 0c88ee5b7523e76e290d558c28cd0be48ffad597 | |
| author | Heiko Carstens <heiko.carstens@de.ibm.com> | |
| Fri, 11 Sep 2009 08:28:58 +0000 (11 10:28 +0200) | ||
| committer | Martin Schwidefsky <schwidefsky@de.ibm.com> | |
| Fri, 11 Sep 2009 08:29:53 +0000 (11 10:29 +0200) | ||
| tree | c603735c1012c231a4cc2d315bb30f795e1c4781 | treesnapshot (tar.gz zip) |
| parent | 50aa98bad056a17655864a4d71ebc32d95c629a7 | commitdiff |
[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>
"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>
| arch/s390/kernel/head31.S | diffblobblamehistory | |
| arch/s390/kernel/head64.S | diffblobblamehistory |