Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758373AbbBERUQ (ORCPT ); Thu, 5 Feb 2015 12:20:16 -0500 Received: from mx1.redhat.com ([209.132.183.28]:53152 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758121AbbBERUP (ORCPT ); Thu, 5 Feb 2015 12:20:15 -0500 Date: Thu, 5 Feb 2015 18:18:59 +0100 From: Oleg Nesterov To: Kirill Tkhai Cc: linux-kernel@vger.kernel.org, Andrew Morton , tkhai@yandex.ru Subject: Re: [PATCH] de_thread: Move notify_count write under lock Message-ID: <20150205171858.GA17659@redhat.com> References: <1423142000.6933.3.camel@tkhai> <20150205133829.GA8322@redhat.com> <1423152711.6933.19.camel@tkhai> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1423152711.6933.19.camel@tkhai> User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 808 Lines: 24 On 02/05, Kirill Tkhai wrote: > > Other solution is in the patch below. I like your previous patch more ;) > Can't (sig->notify_count == -1) be visible earlier than tsk->signal->group_exit_task > in exit_notify()? Yes, please see another email I sent. Sorry again for missing your point. > tasklist_lock is held in exit_notify(), but de_thread() actions (notify_count and > group_exit_task writes) are independent from it (another lock is held there). ^^^^^^^^^^^^^^^^^^^^^^^^^^ Yes, I missed this. Oleg. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/