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] [day] [month] [year] [list]
Date:	Mon, 20 Jul 2015 09:39:39 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Mathias Krause <minipli@...glemail.com>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org,
	x86@...nel.org
Subject: Re: [PATCH 0/5] x86: __ref / __refdata cleanup


* Mathias Krause <minipli@...glemail.com> wrote:

> This series drops quite a few -- relatively speaking -- __ref /
> __refdata annotations in the x86 code. They used to be needed in
> __cpuinit times but those are long gone. Now those annotations may
> only serve as an additional error source, hiding legitimate section
> mismatches. So we better get rid of them.
> 
> Please apply.
> 
> 
> Mathias Krause (5):
>   x86, ACPI: Get rid of the acpi_map_cpu() wrapper
>   x86, apic: Drop bogus __refdata annotation of cpu notifier
>   x86, cpuid: Drop bogus __refdata annotation of cpu notifier
>   x86, smpboot: Drop bogus __ref annotation from remove_cpu_from_maps()
>   x86, topology: Drop bogus __ref annotations
> 
>  arch/x86/kernel/acpi/boot.c           |    8 +-------
>  arch/x86/kernel/apic/x2apic_cluster.c |    2 +-
>  arch/x86/kernel/cpuid.c               |    2 +-
>  arch/x86/kernel/smpboot.c             |    2 +-
>  arch/x86/kernel/topology.c            |    4 ++--
>  5 files changed, 6 insertions(+), 12 deletions(-)

Please send a single patch - there's absolutely zero reason to use 5 patches.

Thanks,

	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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ