linux-kernel - Re: Build regressions/improvements in v3.10

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:	Tue, 2 Jul 2013 12:34:11 -0600
From:	Bjorn Helgaas <bhelgaas@...gle.com>
To:	Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:	Linux Kernel Development <linux-kernel@...r.kernel.org>
Subject: Re: Build regressions/improvements in v3.10

On Tue, Jul 2, 2013 at 11:12 AM, Geert Uytterhoeven
<geert@...ux-m68k.org> wrote:
> Below is the list of build error/warning regressions/improvements in
> v3.10[1] compared to v3.9[2].

Thanks for doing this!

>   + warning: vmlinux.o(.text+0x1ad7a4): Section mismatch in reference from the function pwmchip_add() to the function .init.text:pcibios_fixup_bus():  => N/A
>   + warning: vmlinux.o(.text+0x1b18d8): Section mismatch in reference from the function pci_scan_child_bus() to the function .init.text:pcibios_fixup_bus():  => N/A

I understand the second warning, but not the first (reference from
pwmchip_add() to pcibios_fixup_bus()).  I don't think pwmchip_add()
calls pcibios_fixup_bus().  Is the pwmchip_chip() function name
inexact, or is there some other problem here?

I did post patches to fix the pcibios_fixup_bus() implementations that
are incorrectly marked __init.

Bjorn
--
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/