On Thu, 2013-09-12 at 12:32 -0400, Jun Chen wrote: > When try to add node to list in __inet_hash_nolisten function, first get the > list and then to lock for using, but in extremeness case, others can del this > node before locking it, then the node should be null.So this patch try to lock > firstly and then get the list for using to avoid this race condition.
I suspect another bug. This should not happen. Care to describe the problem you got ? Thanks -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
