On Fri, Dec 18, 2015 at 02:13:43PM +0530, [email protected] wrote:
> From: Bhuvanesh Surachari <[email protected]>
>
> In case of error from rt_mutex_start_proxy_lock pi_state is freed
> twice in futex_requeue function. Hence removing free_pi_state in
> else branch and branching to the location where pi_state is freed.
>
> Signed-off-by: Bhuvanesh Surachari <[email protected]>
> Signed-off-by: Andy Lowe <[email protected]>
Apparently inadvertently introduced by:
commit 30a6b8031fe14031ab27c1fa3483cb9780e7f63c
futex: Fix a race condition between REQUEUE_PI and task death
Reviewed-by: Darren Hart <[email protected]>
> ---
> kernel/futex.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/kernel/futex.c b/kernel/futex.c
> index 684d754..264b3f2 100644
> --- a/kernel/futex.c
> +++ b/kernel/futex.c
> @@ -1815,7 +1815,6 @@ retry_private:
> } else if (ret) {
> /* -EDEADLK */
> this->pi_state = NULL;
> - free_pi_state(pi_state);
> goto out_unlock;
> }
> }
> --
> 1.7.9.5
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
Darren Hart
Intel Open Source Technology Center
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
