Re: [RFC v5] wait: prevent exclusive waiter starvation

[Oleg Nesterov <oleg@redhat.com>]

On 01/26, Johannes Weiner wrote:
>
> Another iteration.  I didn't use a general finish_wait_exclusive() but
> a version of this function that just returns whether we were woken
> through the queue or not.

But if your helper (finish_wait_woken) returns true, we always need
to wakeup the next waiter, or we don't need to use it. So why not
place the wakeup in the helper itself?

> --- a/include/linux/wait.h
> +++ b/include/linux/wait.h
> @@ -333,16 +333,20 @@ do {									\
>  	for (;;) {							\
>  		prepare_to_wait_exclusive(&wq, &__wait,			\
>  					TASK_INTERRUPTIBLE);		\
> -		if (condition)						\
> +		if (condition) {					\
> +			finish_wait(&wq, &__wait);			\
>  			break;						\
> +		}							\
>  		if (!signal_pending(current)) {				\
>  			schedule();					\
>  			continue;					\
>  		}							\
>  		ret = -ERESTARTSYS;					\
> +		if (finish_wait_woken(&wq, &__wait))			\
> +			__wake_up_common(&wq, TASK_INTERRUPTIBLE,	\

No, we can't use __wake_up_common() without wq->lock.

Oleg.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>