65 	unsigned long blocked;  member
80 #define BLOCKED 0  macro
116 	 * As in pppoatm_pop(), it's safe to clear the BLOCKED bit here because  in pppoatm_release_cb()
121 	 * set the BLOCKED bit while the socket is still locked. We know that  in pppoatm_release_cb()
124 	if (test_and_clear_bit(BLOCKED, &pvcc->blocked))  in pppoatm_release_cb()
132  * but we also need to wake up the device if we blocked it
143 	 * fear of race conditions where we clear the BLOCKED flag just as we  in pppoatm_pop()
153 	 * So if the CPU in pppoatm_send() has already set the BLOCKED bit and  in pppoatm_pop()
156 	 * BLOCKED bit yet, that's fine too because of the double check in  in pppoatm_pop()
159 	if (test_and_clear_bit(BLOCKED, &pvcc->blocked))  in pppoatm_pop()
254 	test_and_set_bit(BLOCKED, &pvcc->blocked);  in pppoatm_may_send()
258 	 * last packet in the queue, *just* before we set the BLOCKED  in pppoatm_may_send()
260 	 * remain permanently blocked. Cope with that race by checking  in pppoatm_may_send()
263 	 * the BLOCKED flag set, since it's only used as a trigger to  in pppoatm_may_send()
266 	 * space on the queue yet, then it hasn't checked the BLOCKED  in pppoatm_may_send()
308 		test_and_set_bit(BLOCKED, &pvcc->blocked);  in pppoatm_send()