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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Mon, 10 Jan 2022 21:43:36 +0100
From:   Thomas Gleixner <>
To:     Heiner Kallweit <>,
        kernel test robot <>
Cc:     Michael Kelley <>,
        Nishanth Menon <>, Jason Gunthorpe <>,
        LKML <>,,,,,
        "David S. Miller" <>,
        Jakub Kicinski <>,
Subject: Re: [genirq/msi] 495c66aca3:

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?




Powered by blists - more mailing lists