diff options
| author | Heiko Carstens <heiko.carstens@de.ibm.com> | 2013-06-19 09:16:54 +0200 |
|---|---|---|
| committer | Martin Schwidefsky <schwidefsky@de.ibm.com> | 2013-06-19 15:36:16 +0200 |
| commit | 35b03aec919c952e67b0b093638e0d79b468f9bc (patch) | |
| tree | 34b38d974ccb0b3d267d338041397e8eecc720d9 /fs/xattr.c | |
| parent | 4026099a3118a1e038c48f3f85203a674938025b (diff) | |
| download | op-kernel-dev-35b03aec919c952e67b0b093638e0d79b468f9bc.zip op-kernel-dev-35b03aec919c952e67b0b093638e0d79b468f9bc.tar.gz | |
s390/mem_detect: fix memory hole handling
With git commit 996b4a7d "s390/mem_detect: remove artificial kdump
memory types" the memory detection code got simplified.
As a side effect the array that describes memory chunks may now
contain empty (zeroed) entries.
All call sites can handle this except for
drivers/s390/char/zcore.c::zcore_memmap_open
which has a really odd user space interface. The easiest fix is to
change the memory hole handling code, so that no empty entries exist
before the last valid entry is reached.
Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
Diffstat (limited to 'fs/xattr.c')
0 files changed, 0 insertions, 0 deletions
