linux-kernel - Re: [EDT][PATCH] kernel/exit.c : Fix missing read

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 21 May 2015 20:16:16 +0200
From:	Oleg Nesterov <oleg@...hat.com>
To:	Maninder Singh <maninder1.s@...sung.com>
Cc:	akpm@...ux-foundation.org, mhocko@...e.cz, peterz@...radead.org,
	mingo@...nel.org, riel@...hat.com, ionut.m.alexa@...il.com,
	peter@...leysoftware.com, linux-kernel@...r.kernel.org,
	"v.narang@...sung.com" <v.narang@...sung.com>,
	AKHILESH KUMAR <akhilesh.k@...sung.com>
Subject: Re: [EDT][PATCH] kernel/exit.c : Fix missing read_unlock

On 05/21, Maninder Singh wrote:
>
>  EP-F6AA0618C49C4AEDA73BFF1B39950BAB
> Hi,
>
> From: Maninder Singh <maninder1.s@...sung.com>
>
> Subject: [PATCH 1/1] kernel/exit.c : Fix missing task_unlock
>
> This patch adds missing read_unlock if do_wait_thread or ptrace_do_wait
> returns non zero.

Confused...

wait_consider_task() should drop tasklist_lock if it returns non-zero?


> --- a/kernel/exit.c
> +++ b/kernel/exit.c
> @@ -1486,12 +1486,16 @@ repeat:
>  	tsk = current;
>  	do {
>  		retval = do_wait_thread(wo, tsk);
> -		if (retval)
> +		if (retval) {
> +			read_unlock(&tasklist_lock);
>  			goto end;
> +		}
>
>  		retval = ptrace_do_wait(wo, tsk);
> -		if (retval)
> +		if (retval) {
> +			read_unlock(&tasklist_lock);
>  			goto end;
> +		}

Well, the patch is obviously wrong. Because, again, tasklist_lock was
already unlocked if (say) wait_task_zombie() reaps a child.

If you think there is a case which forgets to unlock, please tell us
more.

Oleg.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/