On Fri, 2011-10-21 at 18:57 +0200, Bart Van Assche wrote: > Register transport attributes after the attribute array has been > set up instead of before. The current code is racy because there > is no guarantee that the CPU examining the attribute container > will see all values written to the container. I don't agree with this change log. As far as the kernel is concerned, nothing happens until that function returns because the only way to use anything is to get a match to succeed, and they all check for ->transportt which will be NULL. I can accept that it's best practise to initialise something before registering it, because the reverse excites everyone's bogosity sensors, it's just not a bug in this case. James -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
