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]
Message-ID: <20211228155845.2609de2e@kicinski-fedora-PC1C0HJN.hsd1.ca.comcast.net>
Date:   Tue, 28 Dec 2021 15:58:45 -0800
From:   Jakub Kicinski <kuba@...nel.org>
To:     Heiner Kallweit <hkallweit1@...il.com>
Cc:     David Miller <davem@...emloft.net>,
        Realtek linux nic maintainers <nic_swsd@...ltek.com>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH net-next] r8169: don't use pci_irq_vector() in atomic
 context

On Tue, 28 Dec 2021 23:11:47 +0100 Heiner Kallweit wrote:
> On 28.12.2021 22:02, Heiner Kallweit wrote:
> > From: Thomas Gleixner <tglx@...utronix.de>
> > 
> > Since referenced change pci_irq_vector() can't be used in atomic
> > context any longer. This conflicts with our usage of this function
> > in rtl8169_netpoll(). Therefore store the interrupt number in
> > struct rtl8169_private.
> > 
> > Fixes: 495c66aca3da ("genirq/msi: Convert to new functions")  
> 
> Seeing the "fail" in patchwork: The referenced commit just recently
> showed up in linux-next and isn't in net-next yet.

Thanks for the heads up, looks safe to apply.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ