linux-kernel - Re: [PATCH] x86, efi: Allow slash in file path of initrd

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

Message-ID: <1357577053.8203.66.camel@mfleming-mobl1.ger.corp.intel.com>
Date:	Mon, 07 Jan 2013 16:44:13 +0000
From:	Matt Fleming <matt.fleming@...el.com>
To:	"Lee, Chun-Yi" <joeyli.kernel@...il.com>
Cc:	linux-kernel@...r.kernel.org, "Lee, Chun-Yi" <jlee@...e.com>,
	Matthew Garrett <mjg59@...f.ucam.org>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [PATCH] x86, efi: Allow slash in file path of initrd

On Thu, 2012-12-20 at 19:33 +0800, Lee, Chun-Yi wrote:
> When initrd file didn't put at the same place with stub kernel, we
> need give the file path of initrd, but need use backslash to separate
> directory and file. It's not friendly to unix/linux user, and not so
> intuitive for bootloader forward paramters to efi stub kernel by
> chainloading.
> 
> This patch add support to handle_ramdisks for allow slash in file path
> of initrd, it convert slash to backlash when parsing path.
> 
> In additional, this patch also separates print code of efi_char16_t from
> efi_printk, and print out the path/filename of initrd when failed to open
> initrd file. It's good for debug and discover typo.
> 
> Cc: Matthew Garrett <mjg59@...f.ucam.org>
> Cc: H. Peter Anvin <hpa@...or.com>
> Cc: Matt Fleming <matt.fleming@...el.com> 
> Signed-off-by: Lee, Chun-Yi <jlee@...e.com>
> ---
>  arch/x86/boot/compressed/eboot.c |   26 +++++++++++++++++++-------
>  1 files changed, 19 insertions(+), 7 deletions(-)

Thanks, I've queued this up. 


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