linux-kernel - Preemption VS Interrupts

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>] [day] [month] [year] [list]

Message-ID: <CAHP4M8WHcDABX-Vwr6kndoFTJKA7Sd3euruabDfXw6SfeqOObw@mail.gmail.com>
Date:   Sun, 10 Dec 2023 15:24:34 +0530
From:   Ajay Garg <ajaygargnsit@...il.com>
To:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Preemption VS Interrupts

Hi everyone.

The API "spin_lock" disables preemption on the local processor.
The API "spin_lock_irqsave" disables preemption on the local
processor, and also disables interrupts on the local processor.

Thus, is disabling-interrupt independent of preemption?
In other words, can an interrupt still "preempt" a critical section
code even if preemption is disabled in the general sense (on a
non-preemptive kernel for example)?

Will be grateful for help in this regard, as it will clear up the
fuzziness going in my head.
Many thanks in advance !

Thanks and Regards,
Ajay