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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 18 Sep 2017 17:56:02 +0200
From:   Arnd Bergmann <>
To:     " bot" <>
Cc:     Kernel Build Reports Mailman List 
        Ralf Baechle <>,
        Steve French <>,
        Linux Kernel Mailing List <>,
        Lorenzo Pieralisi <>
Subject: Re: mainline/master build: 212 builds: 2 failed, 210 passed, 2
 errors, 55 warnings (v4.14-rc1-9-g0666f560b71b)

On Sun, Sep 17, 2017 at 7:04 PM, bot <> wrote:

> Errors summary:
> 1 arch/mips/pmcs-msp71xx/msp_smp.c:72:2: error: implicit declaration of function 'set_vi_handler' [-Werror=implicit-function-declaration]

Sent a patch now

> Warnings summary:
> 19 fs/cifs/smb2ops.c:563:1: warning: 'smb2_set_ea' defined but not used [-Wunused-function]
> 19 fs/cifs/smb2ops.c:513:1: warning: 'smb2_query_eas' defined but not used [-Wunused-function]

Steve French merged my patch, should be upstream soon.

> 6 include/linux/kernel.h:60:38: warning: division by zero [-Wdiv-by-zero]

Geert sent a patch last week.

> 1 arch/arm/configs/zeus_defconfig:115:warning: symbol value 'm' invalid for FRAMEBUFFER_CONSOLE
> 1 arch/arm/configs/viper_defconfig:116:warning: symbol value 'm' invalid for FRAMEBUFFER_CONSOLE
> 1 arch/arm/configs/pxa_defconfig:474:warning: symbol value 'm' invalid for FRAMEBUFFER_CONSOLE

Sent a patch now

> Section mismatches summary:
> 27 WARNING: modpost: Found 1 section mismatch(es).
> 6 WARNING: modpost: Found 2 section mismatch(es).

These are all MIPS warnings caused by Lorenzo's

04c81c7293df ("MIPS: PCI: Replace pci_fixup_irqs() call with host
bridge IRQ mapping hooks")

The problem is that now we can reference pci_fixup_irqs
from a function that is not marked __init, and probably
should not be, since pcibios_scanbus() itself can be called
at any time. Even before Lorenzo's change, having
pcibios_map_irq as an __init function was problematic AFAICT
on any platform that has hotplug-capable PCIe slots, or
that can have a PCI host bridge driver in a loadable module.

The safe fix would be to remove all the __init annotations as well
as the __initdata and __initconst annotations on data referenced
by the map_irq functions.


Powered by blists - more mailing lists