| 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
| ||
|
Date: Wed, 30 Aug 2006 07:42:32 +0530 From: "Rick Brown" <rick.brown.3@...il.com> To: kernelnewbies@...linux.org, linux-newbie@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Spinlock query Hi, In my driver (Process context), I have written the following code: -------------------------------------------- spin_lock(lock) ... //Critical section to manipulate driver data ... spin_u lock(lock) --------------------------------------------- I have written similar code in my interrupt handler (Interrupt context). The driver data is not accessed from anywhere else. Is my code safe from any potential concurrency issues? Is there a need to use spin_lock_irqsave()? In both the places? I intend to run the driver on SMP machine. Regards, Rick - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists