Revision 85de7fac3990cf0c0736edc83856add2e648c76a authored by Marek Vasut on 21 November 2012, 05:19:06 UTC, committed by Wolfram Sang on 21 January 2013, 15:26:29 UTC
The init_completion() call does reinit not only the variable carrying
the flag that the completion finished, but also initialized the
waitqueue associated with the completion. On the contrary, the
INIT_COMPLETION() call only reinits the flag.

In case there was anything still stuck in the waitqueue, subsequent call
to init_completion() would be able to create possible race condition. This
patch uses the proper function and moves init_completion() into .probe() call
of the driver, to be issued only once.

Note that such scenario is impossible, since two threads can never enter the
mxs_i2c_xfer_msg(), since whole this section is protected by mutex in I2C core.
This by no means allows this issue to exit though.

Signed-off-by: Marek Vasut <marex@denx.de>
Signed-off-by: Wolfram Sang <w.sang@pengutronix.de>
1 parent 7d1f9ae
History
File Mode Size
Kconfig -rw-r--r-- 561 bytes
Makefile -rw-r--r-- 218 bytes
crypto.c -rw-r--r-- 67.7 KB
debug.c -rw-r--r-- 3.8 KB
dentry.c -rw-r--r-- 2.7 KB
ecryptfs_kernel.h -rw-r--r-- 24.1 KB
file.c -rw-r--r-- 10.7 KB
inode.c -rw-r--r-- 32.8 KB
keystore.c -rw-r--r-- 79.1 KB
kthread.c -rw-r--r-- 4.9 KB
main.c -rw-r--r-- 25.1 KB
messaging.c -rw-r--r-- 14.0 KB
miscdev.c -rw-r--r-- 15.0 KB
mmap.c -rw-r--r-- 16.0 KB
read_write.c -rw-r--r-- 8.7 KB
super.c -rw-r--r-- 6.0 KB

back to top