path: root/ipc/msg.c
diff options
authorLinus Torvalds <torvalds@g5.osdl.org>2006-11-04 09:55:00 -0800
committerLinus Torvalds <torvalds@g5.osdl.org>2006-11-04 09:55:00 -0800
commit80491eb90c750fcd7d13830062f27ae9b7cc5f75 (patch)
tree81d506d9559c13c090cc853d13f48fcf982795df /ipc/msg.c
parentddac0d39cf437d02fde9795ae57d9c4b4c146de9 (diff)
Revert unintentional "volatile" changes in ipc/msg.c
Commit 5a06a363ef48444186f18095ae1b932dddbbfa89 ("[PATCH] ipc/msg.c: clean up coding style") breaks fakeroot on Alpha (variously hangs or oopses), according to a report by Falk Hueffner. The fact that the code seems to rely on compiler access ordering through the use of "volatile" is a pretty certain sign that the code has locking problems, and we should fix those properly and then remove the whole "volatile" entirely. But in the meantime, the movement of "volatile" was unintentional, and should be reverted. Cc: Falk Hueffner <falk@debian.org> Cc: Andrew Morton <akpm@osdl.org> Acked-by: Ingo Molnar <mingo@elte.hu> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'ipc/msg.c')
1 files changed, 1 insertions, 1 deletions
diff --git a/ipc/msg.c b/ipc/msg.c
index 600e06f943a..1266b1d0c8e 100644
--- a/ipc/msg.c
+++ b/ipc/msg.c
@@ -52,7 +52,7 @@ struct msg_receiver {
long r_msgtype;
long r_maxsize;
- volatile struct msg_msg *r_msg;
+ struct msg_msg *volatile r_msg;
/* one msg_sender for each sleeping sender */