65 	unsigned long blocked;  member
80 #define BLOCKED 0  macro
114 	 * As in pppoatm_pop(), it's safe to clear the BLOCKED bit here because  in pppoatm_release_cb()
119 	 * set the BLOCKED bit while the socket is still locked. We know that  in pppoatm_release_cb()
122 	if (test_and_clear_bit(BLOCKED, &pvcc->blocked))  in pppoatm_release_cb()
130  * but we also need to wake up the device if we blocked it
141 	 * fear of race conditions where we clear the BLOCKED flag just as we  in pppoatm_pop()
151 	 * So if the CPU in pppoatm_send() has already set the BLOCKED bit and  in pppoatm_pop()
154 	 * BLOCKED bit yet, that's fine too because of the double check in  in pppoatm_pop()
157 	if (test_and_clear_bit(BLOCKED, &pvcc->blocked))  in pppoatm_pop()
252 	test_and_set_bit(BLOCKED, &pvcc->blocked);  in pppoatm_may_send()
256 	 * last packet in the queue, *just* before we set the BLOCKED  in pppoatm_may_send()
258 	 * remain permanently blocked. Cope with that race by checking  in pppoatm_may_send()
261 	 * the BLOCKED flag set, since it's only used as a trigger to  in pppoatm_may_send()
264 	 * space on the queue yet, then it hasn't checked the BLOCKED  in pppoatm_may_send()
306 		test_and_set_bit(BLOCKED, &pvcc->blocked);  in pppoatm_send()