linux-kernel - Re: [PATCH v2] unicore32: standardize /proc/iomem "Kernel code" name

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: <1323737423.32086.18.camel@epip-laptop>
Date:	Tue, 13 Dec 2011 08:50:23 +0800
From:	Guan Xuetao <gxt@...c.pku.edu.cn>
To:	Kees Cook <keescook@...omium.org>
Cc:	linux-kernel@...r.kernel.org, Arnd Bergmann <arnd@...db.de>
Subject: Re: [PATCH v2] unicore32: standardize /proc/iomem "Kernel code"
 name

On Mon, 2011-12-12 at 15:04 -0800, Kees Cook wrote:
> All other ports use "Kernel code" to identify the Kernel text segment
> in /proc/iomem. Change the unicore32 resources to do the same.
> 
> Signed-off-by: Kees Cook <keescook@...omium.org>
> Acked-by: Arnd Bergmann <arnd@...db.de>

Thanks.
I have pushed this patch into my repo.

Guan Xuetao

> ---
> v2: Fixed my copy/paste-o.
> ---
>  arch/unicore32/kernel/setup.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/arch/unicore32/kernel/setup.c b/arch/unicore32/kernel/setup.c
> index 471b6bc..2a64061 100644
> --- a/arch/unicore32/kernel/setup.c
> +++ b/arch/unicore32/kernel/setup.c
> @@ -64,7 +64,7 @@ static char default_command_line[COMMAND_LINE_SIZE] __initdata = CONFIG_CMDLINE;
>   */
>  static struct resource mem_res[] = {
>  	{
> -		.name = "Kernel text",
> +		.name = "Kernel code",
>  		.start = 0,
>  		.end = 0,
>  		.flags = IORESOURCE_MEM
> -- 
> 1.7.5.4
> 
> 


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