summaryrefslogtreecommitdiff
path: root/vmcore-dmesg/vmcore-dmesg.8
diff options
context:
space:
mode:
authorCong Wang <xiyou.wangcong@gmail.com>2017-11-07 16:03:31 -0800
committerSimon Horman <horms@verge.net.au>2017-11-09 10:20:56 +0900
commite08d26b3b7f1e985cc4624e90b8636ac6063be18 (patch)
tree717f88da59ce1fddeaad96b94c9a33aeaad77027 /vmcore-dmesg/vmcore-dmesg.8
parent9004e19ca2e7ac093ae08fbbcf00018a9a4a664c (diff)
vmcore-dmesg: avoid allocating large memory chunk for log buf
In kdump kernel, we got: Saving vmcore-dmesg.txt Failed to malloc 67108864 bytes for the logbuf: Cannot allocate memory Apparently 64M is too luxury for a kdump kernel which only has 128M in total. We can avoid allocating such a large memory chunk, instead just allocate a smaller chunk inside the loop each time. Verify the result by comparing the vmcore-dmesg output with and without this patch. Cc: Simon Horman <horms@verge.net.au> Reviewed-by: Dave Young <dyoung@redhat.com> Reviewed-by: Pratyush Anand <panand@redhat.com> Signed-off-by: Cong Wang <xiyou.wangcong@gmail.com> Signed-off-by: Simon Horman <horms@verge.net.au>
Diffstat (limited to 'vmcore-dmesg/vmcore-dmesg.8')
0 files changed, 0 insertions, 0 deletions