linux-kernel - Re: [PATCH v5 1/5] vmcore: Introduce ELF header in new memory feature

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 14 Jun 2013 14:54:02 -0400
From:	Vivek Goyal <vgoyal@...hat.com>
To:	Michael Holzheu <holzheu@...ux.vnet.ibm.com>
Cc:	HATAYAMA Daisuke <d.hatayama@...fujitsu.com>,
	Jan Willeke <willeke@...ibm.com>,
	Martin Schwidefsky <schwidefsky@...ibm.com>,
	Heiko Carstens <heiko.carstens@...ibm.com>,
	linux-kernel@...r.kernel.org, kexec@...ts.infradead.org
Subject: Re: [PATCH v5 1/5] vmcore: Introduce ELF header in new memory feature

On Fri, Jun 07, 2013 at 06:55:57PM +0200, Michael Holzheu wrote:

[..]
> @@ -935,10 +967,17 @@ static int __init vmcore_init(void)
>  {
>  	int rc = 0;
>  
> -	/* If elfcorehdr= has been passed in cmdline, then capture the dump.*/
> -	if (!(is_vmcore_usable()))
> -		return rc;
> +	/*
> +	 * If elfcorehdr= has not been passed in cmdline, try to get the
> +	 * header from 2nd kernel, then capture the dump.
> +	 */
> +	if (!(is_vmcore_usable())) {
> +		rc = elfcorehdr_alloc();
> +		if (rc)
> +			return rc;
> +	}

Hi Michael,

Patch description says that elfcorehdr_alloc() returns the addr and 
size of elf headers. But that does not seem to be the case here. Has
it been modified in later patches.

Also will it be better if we call elfcorehdr_alloc() always and then
check for is_vmcore_usable().

Something like.

elfcorehdr_addr = elfcorehdr_alloc()
if (elfcorehdr_addr < )
	return elfcorehdr_addr

if (!(is_vmcore_usable()))
	return error

Thanks
Vivek
--
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/