diff options
| author | Li Zhong <zhong@linux.vnet.ibm.com> | 2014-11-17 02:52:30 (GMT) |
|---|---|---|
| committer | Michael Ellerman <mpe@ellerman.id.au> | 2014-11-19 05:09:13 (GMT) |
| commit | a49ab6eeebe5624d51466969a7bac611231eede8 (patch) | |
| tree | 5f907029857ad1aad276376699bbbdfd04f3f6cc /arch/powerpc/lib/alloc.c | |
| parent | 35891d40bfc4f41fc627abb757c0894c0028f3ab (diff) | |
| download | linux-a49ab6eeebe5624d51466969a7bac611231eede8.tar.xz | |
powerpc/pseries: Initialise nvram_pstore_info's buf_lock
nvram_pstore_info's buf_lock is not initialized before registering,
which is clearly incorrect.
It causes some strange behavior when trying to obtain the lock during
kdump process.
On a UP configuration, the console stopped for a couple of seconds, then
"lockup suspected" warning printed out, but then it continued to run.
So try lock fails, and lockup reported, but then arch_spin_lock()
passes.
Signed-off-by: Li Zhong <zhong@linux.vnet.ibm.com>
[mpe: Edited changelog]
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Diffstat (limited to 'arch/powerpc/lib/alloc.c')
0 files changed, 0 insertions, 0 deletions