linux-kernel - Re: [PATCH 08/16] x86: use get

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]

Message-Id: <20080223.183901.201654325.xiyou.wangcong@gmail.com>
Date:	Sat, 23 Feb 2008 18:39:01 +0800 (CST)
From:	WANG Cong <xiyou.wangcong@...il.com>
To:	mingo@...e.hu
Cc:	akpm@...l.org, linux-kernel@...r.kernel.org, mingo@...hat.com
Subject: Re: [PATCH 08/16] x86: use get_personality()

From: Ingo Molnar <mingo@...e.hu>
Subject: Re: [PATCH 08/16] x86: use get_personality()
Date: Sat, 23 Feb 2008 11:19:54 +0100
Message-ID: <20080223101954.GA28929@...e.hu>

> 
> * Ingo Molnar <mingo@...e.hu> wrote:
> 
> > * WANG Cong <xiyou.wangcong@...il.com> wrote:
> > 
> > > Use get_personality() macro instead of explicit reference for x86 
> > > code.
> > 
> > thanks, applied.
> 
> randconfig testing found the following build failures:
> 
>   arch/x86/kernel/process_64.c: In function 'do_arch_prctl':
>   arch/x86/kernel/process_64.c:836: error: called object 'get_current()->personality' is not a function
>   arch/x86/kernel/process_64.c:862: error: called object 'get_current()->personality' is not a function
> 
> so i dropped the patch again. Config attached.
> 
> 	Ingo

Sorry that I didn't mention that this patch should be applied
_after_ [patch 01/16], since in [patch 01/16] I made the macro
get_personality like a function.

Sorry for this. Just wait after [patch 01/16] is applied.

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