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-next>] [day] [month] [year] [list]
Message-ID: <00fb01d3e81b$89b9c2d0$9d2d4870$@lge.com>
Date:   Thu, 10 May 2018 13:58:29 +0900
From:   ·ùÈ£Àº <hoeun.ryu@....com>
To:     <mingo@...nel.org>, <peterz@...radead.org>, <aaron.lu@...el.com>,
        <adobriyan@...il.com>, <frederic@...nel.org>,
        <ying.huang@...el.com>
Cc:     <linux-kernel@...r.kernel.org>
Subject: smp_call_function() friends and irq/bottom_half context

Hi, all.

I'm reading kernel/smp.c code and I found comments on smp_call_function()
and smp_call_function_[single/many]
saying that these functions are cannot be called in interrupt disabled
context or irq/bottom half handlers.

I understand that there is a potential deadlock issue when caller CPU of
the functions is waiting for the completion of the callback of other CPUs.
But I was wondering if this is the case even when the caller CPU doesn't
wait for the completion (wait == 0).

Thank you.


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ