[PATCH 2/2] 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)

[PATCH 1/2] cleanup: move it back from util_lib/elf_info.c

Some code related to vmcore-dmesg.c is put into the util_lib, which is not very reasonable, so lets move it back and tidy up those code. In addition, that will also help to limit the size of vmcore-dmesg.txt. Signed-off-by: Lianbo Jiang --- kexec/arch/arm64/kexec-arm64.c | 2 +-

[PATCH 0/2] Limit the size of vmcore-dmesg.txt to 2G

[PATCH 1/2] cleanup: move it back from util_lib/elf_info.c Some code related to vmcore-dmesg.c is put into the util_lib, which is not very reasonable, so lets move it back and tidy up those code. In addition, that will also help to limit the size of vmcore-dmesg.txt. [PATCH 2/2] Limit the

Re: No compression technique of zImage/uImage detected - ARM

On Tue, Aug 13, 2019 at 7:01 PM Maikel Coenen wrote: > > >02/08/2019, 11:39, "kexec on behalf of Maikel Coenen" > > > >wrote:> >31/07/2019, 14:30, "Bhupesh Sharma" wrote:> > >On Mon, Jul 29, 2019 at 1:36 PM Maikel Coenen > >wrote: > > > > > > > > > On 29/07/2019, 07:02, "Bhupesh Sharma"

Re: [PATCH 3/6] Avoid build warning when !CONFIG_KEXEC_SIG

On Tue, Aug 13, 2019 at 10:24 PM Dave Young wrote: > I can not get the whole thread, also not sure which tree it should > apply. This should be against -next. > Also I think it should be good to split the preparation piece of kexec > and send them separately. Since it is improve the signature