lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:	Sat, 15 Mar 2014 08:09:38 -0700
From:	Prasad Koya <prasad.koya@...il.com>
To:	LKML <linux-kernel@...r.kernel.org>
Subject: Fwd: vmcore-dmesg ends with "No program header covering vaddr"

Forwarding to lkml. If there is any other relevant mailing list, pl let me know.


---------- Forwarded message ----------
From: Prasad Koya <prasad.koya@...il.com>
Date: Fri, Mar 14, 2014 at 10:39 PM
Subject: vmcore-dmesg ends with "No program header covering vaddr"
To: kexec@...ts.infradead.org


Hi

I'm increasing dmesg buffer size at runtime by passing log_buf_len=1M
(or 512K) at command line. At compile time, I have LOG_BUF_LEN as
256K. However, when this kernel crashes (crashkernel set at 64M),
vmcore-dmesg fails with below error.

No program header covering vaddr 0xffff88013ff00000found kexec bug?

Am I missing something here?

Thank you.

Here are some debugs I added to kernel. This is with 3.4 kernel and
I've tried with kexec-tools-2.0.4.

[    0.000000] log_buf_len_setup: log_buf_len 262144 new 1048576
ffffffff8170b140
[    0.000000] setup_log_buf: early 1 262144 new_log_buf_len 1048576
[    0.000000] log_buf_len: 1048576 ffff880037d58000
[    0.000000] early log buf free: 258671(98%)
[    0.000000] setup_log_buf: early 0 1048576 new_log_buf_len 0
[    0.503752] log_buf_kexec_setup: lbl 1048576 new 0 ffffffff816198c4
logbuf ffff880037d58000
In kdump, running vmcore_dmesg /proc/vmcore
No program header covering vaddr 0xffff88013ff00000found kexec bug?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ