diff options
| author | Lianbo Jiang <lijiang@redhat.com> | 2019-08-23 20:05:39 +0800 |
|---|---|---|
| committer | Simon Horman <horms@verge.net.au> | 2019-09-08 13:26:56 +0100 |
| commit | fa3f0ed47f3e6dbee485722d13713ad495571b7e (patch) | |
| tree | 10799e8006176e42e4a011d3c1950a2a0290069b /kexec/firmware_memmap.c | |
| parent | a7c4cb8e998571cb3dd62e907935a1e052b15d6c (diff) | |
Limit the size of vmcore-dmesg.txt to 2G
With some corrupted vmcore files, the vmcore-dmesg.txt file may grow
forever till the kdump disk becomes full, and also probably causes
the disk error messages as follow:
...
sd 0:0:0:0: [sda] tag#6 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
sd 0:0:0:0: [sda] tag#6 CDB: Read(10) 28 00 08 06 4c 98 00 00 08 00
blk_update_request: I/O error, dev sda, sector 134630552
sd 0:0:0:0: [sda] tag#7 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
sd 0:0:0:0: [sda] tag#7 CDB: Read(10) 28 00 08 06 4c 98 00 00 08 00
blk_update_request: I/O error, dev sda, sector 134630552
...
If vmcore-dmesg.txt occupies the whole disk, the vmcore can not be
saved, this is also a problem.
Lets limit the size of vmcore-dmesg.txt to avoid such problems.
Signed-off-by: Lianbo Jiang <lijiang@redhat.com>
Signed-off-by: Simon Horman <horms@verge.net.au>
Diffstat (limited to 'kexec/firmware_memmap.c')
0 files changed, 0 insertions, 0 deletions