Hello. I am reporting possible data race due to the the absence of memory barriers. I reported a similar issue. Although the previous one turns out to be safe, please examine this issue and let me know your opinion. In btrfs_init_new_device(), a btrfs_device object is allocated and initialized and then links to &root->fs_info->fs_devcies->alloc_list. It seems that a memory barrier is necessary between the initialization and the linking to the list. If these two operations are re-ordered so that executed opposite orders, it may result data race where uninitialized values are read by other threads. For btrfs_init_new_device(), i think __btfs_alloc_chunk() is a suspected to be possible to contribute data race by concurrent execution. Thank you Sincerely Shin Hong -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
