linux-kernel - Re: [git pull] PCI changes for 2.6.30

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]

Date:	Mon, 6 Apr 2009 09:19:31 -0600
From:	Alex Chiang <achiang@...com>
To:	Sam Ravnborg <sam@...nborg.org>
Cc:	Jesse Barnes <jbarnes@...tuousgeek.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org
Subject: Re: [git pull] PCI changes for 2.6.30

* Sam Ravnborg <sam@...nborg.org>:
> > 
> > Reading through Documentation/PCI/pci.txt says that under
> > CONFIG_HOTPLUG, __devinit should be a nop?
> The documentation is not up-to-date in this respect.
> 
> Annotating a function __devinit will no matter the configuration
> locate the code in a section named .devinit.text

Ok, I'll update the documentation.

> We then postprocess this section for illegal references using modpost.
> 
> The PCI_HOTPLUG code has often been troublesome with respect to these checks
> as this code is only relevant if CONFIG_HOTPLUG is enabled
> and will often not even be included in the kernel if not enabled.
> This is true for pci_rescan_bus() for example.
> 
> And we would like to export these symbols too. But we do not allow exported
> symbols to be annotated __devinit as this code will be blown away in some configurations.
> 
> So the correct solution which you also used in your patch is to tell
> modpost to ignore references to *init sections from this specific funtion
> as they are OK.

Does this count as an Acked-by?

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/