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-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 12 May 2020 14:35:17 +0200
From:   Linus Walleij <>
To:     Bjorn Helgaas <>
Cc:     Greg Kroah-Hartman <>,
        Thomas Gleixner <>,
        "Rafael J . Wysocki" <>,
        Aman Sharma <>,
        linux-pci <>,
        "" <>,
        Bjorn Helgaas <>
Subject: Re: [PATCH v2 0/2] PCI: Check for platform_get_irq() failure consistently

On Sat, May 2, 2020 at 12:41 AM Bjorn Helgaas <> wrote:

> From: Bjorn Helgaas <>
> All callers of platform_get_irq() and related functions interpret a
> negative return value as an error.  A few also interpret zero as an error.
> platform_get_irq() should return either a negative error number or a valid
> non-zero IRQ, so there's no need to check for zero.
> This series:
>   - Extends the platform_get_irq() function comment to say it returns a
>     non-zero IRQ number or a negative error number.
>   - Adds a WARN() if platform_get_irq() ever *does* return zero (this would
>     be a bug in the underlying arch code, and most callers are not prepared
>     for this).
>   - Updates drivers/pci/ to check consistently using "irq < 0".
> This is based on Aman's series [1].  I propose to merge this via the PCI
> tree, given acks from Greg and Thomas.
> [1]

Makes sense to me.
Acked-by: Linus Walleij <>

for the series.

Linus Walleij

Powered by blists - more mailing lists