Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp6893094imu; Mon, 3 Dec 2018 04:40:34 -0800 (PST) X-Google-Smtp-Source: AFSGD/Uj1DfCWbxBNnIC5b+F9nyTsMqSm/Tj6XPgpgKncVaAbYQqgSJxOEHAW7+HmyllEYEfhBMX X-Received: by 2002:a62:30c3:: with SMTP id w186mr15806012pfw.39.1543840834770; Mon, 03 Dec 2018 04:40:34 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1543840834; cv=none; d=google.com; s=arc-20160816; b=r4nlNp5MckivdveI2K2ZSbAqt2bc6MnCHOiSdE0wLpvx6zuSfdnrt34fsH6yCWn0yL l4FYdJ+dM8D1XMC+xFHHUc1cqRWntURdzwyiGiK9OFgxIzcB5kxw6PMQiK8LsU9aG2wZ Hua89YvnBW3HVrC+7Zyy5ZIVTKuToHUvonbL4Jt/ZC7OaMkKzrSxKN7fpDhxPkeW4mOp lQbBmnQMqZzVDDbVr9fiBAPGkWlkbmSdR7ES0VvrSptbVXYxTgbh3tiWMtoarzxBndF4 EVsqbblNyypPNN4V4L8zsublMUB8iyf5dlrVY4EMywz2x5JDLZAU5rxID3t3OkWk0OaR Ch3Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=NG0WJrJTNCbrq+EJ+C00+Grs4HsNv9G75YLtYA4OHlg=; b=QTZuFs5mBRl3b9Zu152rqGQOL0FoHXqTwq+liotlSWi6AufDW47pnDg2XkOLrfOjpU zq4nAjk9W6dytugiMBQPLs8pDBOv8e0U02ok0dP9/sKL595L6SJbHvdcY/wVfcQW+7uh jF35GiVbhUIrxLEjhLJ9Y57+3fGcNOAUrM5vdMTJrequ7NRMHz3UCiyN0HvDoXF8/cNr DruHcPaX65K7igGas+DsQJ7p3gnrIXE56a51cFYedzQR9jyVhBI45sXtLehfLcoRu4Gj RLHtcZMQISx0PA6o7x1FHRyGkS8ydalQvOV58/OldHVvWxDMI4ciT2IvsELHhN2zXUXT 9yaA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id t9si12907232plq.337.2018.12.03.04.40.18; Mon, 03 Dec 2018 04:40:34 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726548AbeLCMjz (ORCPT + 99 others); Mon, 3 Dec 2018 07:39:55 -0500 Received: from mx2.suse.de ([195.135.220.15]:39936 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725877AbeLCMjz (ORCPT ); Mon, 3 Dec 2018 07:39:55 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id BFD53AFE8; Mon, 3 Dec 2018 12:39:00 +0000 (UTC) Date: Mon, 3 Dec 2018 13:38:57 +0100 From: Michal Hocko To: Oleg Nesterov Cc: Ingo Molnar , Linus Torvalds , Linux List Kernel Mailing , "Rafael J. Wysocki" , Chanho Min , Thomas Gleixner , Peter Zijlstra , Pavel Machek Subject: Re: [PATCH] Revert "exec: make de_thread() freezable (was: Re: Linux 4.20-rc4) Message-ID: <20181203123857.GS31738@dhcp22.suse.cz> References: <20181203074700.GA21240@gmail.com> <20181203083942.GF31738@dhcp22.suse.cz> <20181203123149.GB31795@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20181203123149.GB31795@redhat.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon 03-12-18 13:31:49, Oleg Nesterov wrote: > On 12/03, Michal Hocko wrote: > > > > Now, I wouldn't mind to revert this because the code is really old and > > we haven't seen many bug reports about failing suspend yet. But what is > > the actual plan to make this work properly? > > I don't see a simple solution... > > But we need to fix exec/de_thread anyway, then we can probably reconsider > this patch. My concern is that de_thread fix might be too disruptive for stable kernels while we might want to have a simple enough fix for the the suspend issue in the meantime. That was actually the primary reason I've acked the hack even though I didn't like it. So can we find a way to shut the lockdep up when this is not really a deadlock? Or maybe this really is one and then we need a real fix for stable as well. -- Michal Hocko SUSE Labs