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: Mon, 6 Nov 2006 18:03:29 +0300 From: Oleg Nesterov <oleg@...sign.ru> To: David Howells <dhowells@...hat.com> Cc: Steven Rostedt <rostedt@...dmis.org>, Andrew Morton <akpm@...l.org>, Linus Torvalds <torvalds@...l.org>, linux-kernel@...r.kernel.org Subject: [PATCH] a minor fix for set_mb() in Documentation/memory-barriers.txt set_mb() is used by set_current_state() which needs mb(), not wmb(). I think it would be right to assume that set_mb() implies mb(), all arches seem to do just this. Signed-off-by: Oleg Nesterov <oleg@...sign.ru> --- d/Documentation/memory-barriers.txt~ 2006-11-06 17:43:36.000000000 +0300 +++ d/Documentation/memory-barriers.txt 2006-11-06 17:44:26.000000000 +0300 @@ -1016,7 +1016,7 @@ There are some more advanced barrier fun (*) set_mb(var, value) - This assigns the value to the variable and then inserts at least a write + This assigns the value to the variable and then inserts a full memory barrier after it, depending on the function. It isn't guaranteed to insert anything more than a compiler barrier in a UP compilation. - 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