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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 10 Jan 2022 21:43:36 +0100 From: Thomas Gleixner <tglx@...utronix.de> To: Heiner Kallweit <hkallweit1@...il.com>, kernel test robot <oliver.sang@...el.com> Cc: Michael Kelley <mikelley@...rosoft.com>, Nishanth Menon <nm@...com>, Jason Gunthorpe <jgg@...dia.com>, LKML <linux-kernel@...r.kernel.org>, x86@...nel.org, lkp@...ts.01.org, lkp@...el.com, nic_swsd@...ltek.com, "David S. Miller" <davem@...emloft.net>, Jakub Kicinski <kuba@...nel.org>, netdev@...r.kernel.org Subject: Re: [genirq/msi] 495c66aca3: BUG:sleeping_function_called_from_invalid_context_at_kernel/locking/mutex.c On Tue, Dec 28 2021 at 20:25, Heiner Kallweit wrote: > On 28.12.2021 19:40, Thomas Gleixner wrote: >> if (jumbo_max) >> netdev_info(dev, "jumbo features [frames: %d bytes, tx checksumming: %s]\n", > > Thanks for the patch, I'll submit it with your SoB. Thank you! > Apart from pci_irq_vector() incl. underlying msi_get_virq(), are there > more functions that must not be called from atomic context any longer? I don't think so. The allocation/free functions were always restricted to preemptible context. > Maybe the new constraint should be added to kernel-doc of affected > functions? Probably. Thanks, tglx
Powered by blists - more mailing lists