linux-kernel - Question on Atomic operations

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: <309a667c0608292249y3a5173a1uc815cf5e265d332c@mail.gmail.com>
Date:	Wed, 30 Aug 2006 11:19:00 +0530
From:	"Devesh Sharma" <devesh28@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: Question on Atomic operations

Hello list,

The documentation related to atomic operations says that the following
functions should be called in SMP safe maner

 void atomic_add(int i, atomic_t *v);
 void atomic_sub(int i, atomic_t *v);
 void atomic_inc(atomic_t *v);
 void atomic_dec(atomic_t *v);

since the implementation of these functions are prefixed with LOCK
prefix (On i386 arch.) which either asserts LOCK# signal or performs
cache locking which gauarentees coherency.

Then why these functions should be called in SMP safe manner?
-
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/