linux-kernel - Re: [PATCH] move some .pci_fixup

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: <20110408125110.52aa90c4@jbarnes-desktop>
Date:	Fri, 8 Apr 2011 12:51:10 -0700
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	"Jan Beulich" <JBeulich@...ell.com>
Cc:	<linux-kbuild@...r.kernel.org>, <mingo@...e.hu>,
	<tglx@...utronix.de>, <linux-kernel@...r.kernel.org>,
	<linux-pci@...r.kernel.org>, <hpa@...or.com>
Subject: Re: [PATCH] move some .pci_fixup_* sections into .init

On Wed, 09 Feb 2011 08:47:47 +0000
"Jan Beulich" <JBeulich@...ell.com> wrote:

> .pci_fixup_final is only used from .init.text, and hence can (along
> with the respective handler functions) reside in .init.*.
> 
> Several other .pci_fixup_* sections are needed only during boot and
> suspend/resume, and can therefore be moved into .init.* if
> !CONFIG_PM_OPS.
> 
> While generally section mismatch checking is being turned on by this
> patch for all of .pci_fixup_*, for .pci_fixup_header it is being
> suppressed for the moment as it caused way too much fallout.
> Theoretically, all respective handlers must get their __init/__devinit
> removed, as this gets processed from a non-__init, non-__devinit
> function.
> 
> This also adds a previously missing comma in the definition of
> ALL_INIT_DATA_SECTIONS.
> 
> Signed-off-by: Jan Beulich <jbeulich@...ell.com>
> Cc: H. Peter Anvin <hpa@...or.com>
> Cc: Jesse Barnes <jbarnes@...tuousgeek.org>
> Cc: Thomas Gleixner <tglx@...utronix.de>
> Cc: Ingo Molnar <mingo@...e.hu>

This didn't apply for me, but I'd be happy to take the PCI parts, can
you re-send against my linux-next branch (assuming it's not already
applied to some other tree).

Thanks,
-- 
Jesse Barnes, Intel Open Source Technology Center
--
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/