diff options
| author | Michael Holzheu <holzheu@linux.vnet.ibm.com> | 2010-04-22 17:17:07 +0200 |
|---|---|---|
| committer | Martin Schwidefsky <sky@mschwide.boeblingen.de.ibm.com> | 2010-04-22 17:17:19 +0200 |
| commit | 76ef964c78797f9baed7c2f9a58f696e86d8a048 (patch) | |
| tree | 1f6a4e586682dc979bf8eb284049a29fd00cdac3 /drivers/regulator | |
| parent | 157a1a27d5921fc94db8c14e0d01363d13de99b5 (diff) | |
| download | linux-76ef964c78797f9baed7c2f9a58f696e86d8a048.tar.gz linux-76ef964c78797f9baed7c2f9a58f696e86d8a048.tar.bz2 linux-76ef964c78797f9baed7c2f9a58f696e86d8a048.zip | |
[S390] zcore: Fix reipl device detection
The reipl device information is passed from the kernel to zfcpdump
using a pointer in the lowcore (0xe00) that points to the reipl
information Currently if that pointer is not zero, we copy the reipl
information. If the pointer is not initialized and points outside
the accessible memory, it can happen that the memory copy fails.
In that case we currently stop the initialization of zcore which leads
to a failing kernel dump. The correct behavior is to disable the reipl
after dump and continue with zcore intialization.
Signed-off-by: Michael Holzheu <holzheu@linux.vnet.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
Diffstat (limited to 'drivers/regulator')
0 files changed, 0 insertions, 0 deletions