linux-kernel - Re: [PATCH 1/2] x86: Fixing improper annotation.

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 12 Nov 2008 06:35:19 +0600
From:	"Rakib Mullick" <rakib.mullick@...il.com>
To:	"Ingo Molnar" <mingo@...e.hu>
Cc:	"Rufus & Azrael" <rufus-azrael@...ericable.fr>,
	"Linux-kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/2] x86: Fixing improper annotation.

On 11/11/08, Ingo Molnar <mingo@...e.hu> wrote:

>
> okay - so i wont apply them until the full scope of the problems here
>  is mapped. We might be best off by marking xsave_cntxt_init() non-init
>  altogether for the time being?
But, it's been called from an __init section, it will also trigger an
warning too. So, it
 will remain as it was. If we goes to hunt these warnings ( I mean
we've to replace __init __alloc_bootmem() with __cpuinit
__alloc_bootmem() ) , it's not certain when it will stop. Likely , we
need to replace a lots of __init with __cpuinit.

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