Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp2909465imu; Sun, 11 Nov 2018 03:45:51 -0800 (PST) X-Google-Smtp-Source: AJdET5e92DCFeDHOHHstCXSUG3s6MASkIVyZ/iByc79ouZilGL/pdSn8FopLane2wyr0pntoc96b X-Received: by 2002:a65:4646:: with SMTP id k6mr13709433pgr.153.1541936751918; Sun, 11 Nov 2018 03:45:51 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1541936751; cv=none; d=google.com; s=arc-20160816; b=0tjyJtpDyHNJ4SDKq1XyHp2PbiNpCET3wFR9IwlMZ+pIv3D0gAE9rVXeECQ4b0KPvt ZXDb8wOEiiw2f3OFvkS1bt4ITGep4dHy6D79Rf3clyjzG2kaF+pTvrSKeABFxF/A1teM dUDBSHl857BaUGW9WH7+sX5nDnvQbodJhweWimTJXdY93YYUjz5Sk2MHJcVhuXCIjh0W mlw+imfvMYE+0iYr2G0OKEwd2UMKekBCrD7vjJ28/GUfOzeEFMPKVryYGu3oK+rFTN1j c/kgMUyMUQJhmuzyfHLx+U7doVyHHE/Gb+4gp0Nn+9jMg6kXLXSrPzle8IhQVWEif5cA 36AA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=mQUjfeO5EvjMpSjaS21n/gQhWKHYdRmyWxPHMwgiUwk=; b=PG/IH81/p4RkYzbyX2YgKt2YJ28TGxzWIA8KSaAnbN8+NMF07bXSmOV+5Mec80n49l SkY2Pn7oWyQND07khJ0GVYHPB098k7XfFSblopDS57c3xx1sBZ+DxmmQgDrNJc6+4+Gv +XKACygTQbwG8/89YZbhh1UgOyU/QjXOeSPEKYw3U6mZU5guCOlNrwDcHkO55IkVHKM0 zuHT8Dr/y0N3H8XQjij90TqolGDG0onVF661+SzFKKjGCl4jfTrcB775qrRqPhZcoHiL uRFegRXnEjaZ6NIFLQBbNkh5vccjKXD3Bdic1w3SP5v4AWEoPGIVOEfqKLvEcitdJ5LP gb+w== 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=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f189-v6si15633830pfg.84.2018.11.11.03.45.36; Sun, 11 Nov 2018 03:45:51 -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=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727854AbeKKVde (ORCPT + 99 others); Sun, 11 Nov 2018 16:33:34 -0500 Received: from mail-ed1-f66.google.com ([209.85.208.66]:39391 "EHLO mail-ed1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727556AbeKKVde (ORCPT ); Sun, 11 Nov 2018 16:33:34 -0500 Received: by mail-ed1-f66.google.com with SMTP id b14so2618440edt.6 for ; Sun, 11 Nov 2018 03:45:11 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=mQUjfeO5EvjMpSjaS21n/gQhWKHYdRmyWxPHMwgiUwk=; b=tGBZzeqqvpNwTI9h8i9+GNHMdE22vc2VRilIlkY6UBfLIi3Y6zFJY3uiQZ62UIha1w b1uL7e2vooVCoxgNTndFzqvqLa15QAtmg+VNQW83RrUqiq6cxteF3PkOjOB9qq4QunF8 fPM+zoDfgUE4tT0ftVos0IaikJGwuCq1MOdMR1tTuufnBxuV6PlpHQu0nVOZ0tZ2ca+g CeQLgLCCgk46hYLZ1U7yzrNgJ4Muus01aEQbQM8bBEzh36aBJ7wlwnu1Mgi70NS7FK+L YCkFiexPCD1bnNk+BF+rO8USBmRRpUQJzDDOy2XpNNEzNZgsRA0o+lUDMoywncda3YE4 DpSw== X-Gm-Message-State: AGRZ1gINiceT9PIOx0E9ZcxC075KkkujQJp+f+ZtyqWqfPI0JANga4Y/ tKO6SAngQbLaUE8lk7klLvmQow== X-Received: by 2002:a50:ad9a:: with SMTP id a26-v6mr9413962edd.60.1541936711198; Sun, 11 Nov 2018 03:45:11 -0800 (PST) Received: from dhcp-45-79.space.revspace.nl ([2a01:4f8:1c0c:6c86:74cc:2527:1001:2c5e]) by smtp.gmail.com with ESMTPSA id q3-v6sm1907653ejz.30.2018.11.11.03.45.09 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 11 Nov 2018 03:45:10 -0800 (PST) Subject: Re: [PATCH v1 1/5] drivercore: Revert "deferral race condition fix" To: Andy Shevchenko , Greg Kroah-Hartman Cc: MyungJoo Ham , Chanwoo Choi , linux-usb@vger.kernel.org, Felipe Balbi , Guenter Roeck , Heikki Krogerus , Roger Quadros , linux-pm@vger.kernel.org, "Rafael J. Wysocki" , Sebastian Reichel , linux-omap@vger.kernel.org, Darren Hart , platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org, Chen-Yu Tsai , Grant Likely , Peter Ujfalusi , Mark Brown , Andrzej Hajda References: <20181110181101.24557-1-andriy.shevchenko@linux.intel.com> <20181110182622.GA32657@kroah.com> <20181110183629.GE10650@smile.fi.intel.com> From: Hans de Goede Message-ID: Date: Sun, 11 Nov 2018 12:45:08 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.3.0 MIME-Version: 1.0 In-Reply-To: <20181110183629.GE10650@smile.fi.intel.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On 11/10/18 7:36 PM, Andy Shevchenko wrote: > On Sat, Nov 10, 2018 at 10:26:22AM -0800, Greg Kroah-Hartman wrote: >> On Sat, Nov 10, 2018 at 08:10:57PM +0200, Andy Shevchenko wrote: >>> Consider the following scenario. >>> >>> There are two independent devices coupled together by functional dependencies: >>> - USB OTG (dwc3-pci) >>> - extcon (tested with extcon-intel-mrfld, not yet in upstream) >>> >>> Each of the driver services a corresponding device is built as a module. In the >>> Buildroot environment the modules are probed by alphabetical ordering of their >>> modaliases. The latter comes to the case when USB OTG driver will be probed >>> first followed by extcon one. >>> >>> So, if the platform anticipates extcon device to be appeared, in the above case >>> we will get deferred probe of USB OTG, because of ordering. >>> >>> Now, a cherry on top of the cake, the deferred probing list contains >>> the only two modules, i.e. USB OTG and extcon. Due to above circumstances, >>> values in the local_trigger_count and deferred_trigger_count are not the same, >>> and thus provokes deferred probe triggering again and again. >>> >>> ... >>> [ 20.678332] platform dwc3.0.auto: Retrying from deferred list >>> [ 20.694743] platform dwc3.0.auto: Driver dwc3 requests probe deferral >>> [ 20.701254] platform dwc3.0.auto: Added to deferred list >>> [ 20.706620] platform dwc3.0.auto: driver_deferred_probe_add_trigger 1 2 >>> [ 20.713732] platform dwc3.0.auto: Retrying from deferred list >>> [ 20.730035] platform dwc3.0.auto: Driver dwc3 requests probe deferral >>> [ 20.736540] platform dwc3.0.auto: Added to deferred list >>> [ 20.741889] platform dwc3.0.auto: driver_deferred_probe_add_trigger 3 4 >>> [ 20.748991] platform dwc3.0.auto: Retrying from deferred list >>> [ 20.765416] platform dwc3.0.auto: Driver dwc3 requests probe deferral >>> [ 20.771914] platform dwc3.0.auto: Added to deferred list >>> [ 20.777279] platform dwc3.0.auto: driver_deferred_probe_add_trigger 5 6 >>> ... >>> >>> Deeper investigation shows the culprit commit 58b116bce136 >>> ("drivercore: deferral race condition fix") which was dedicated to fix some >>> other issue while bringing a regression. >>> >>> This reverts commit 58b116bce13612e5aa6fcd49ecbd4cf8bb59e835 for good until >>> we will have better solution. >>> >>> Cc: Grant Likely >>> Cc: Peter Ujfalusi >>> Cc: Greg Kroah-Hartman >>> Cc: Mark Brown >>> Cc: Felipe Balbi >>> Cc: Andrzej Hajda >>> Signed-off-by: Andy Shevchenko >>> --- >>> drivers/base/dd.c | 27 ++------------------------- >>> 1 file changed, 2 insertions(+), 25 deletions(-) >> >> Shouldn't there be a "Fixes:" line and cc: stable here? > > I'm not sure (yet). I would like to hear from people first, especially from > Grant (I spoke to him already for the matters at ELCE in Edinburg). > > Perhaps, Hans can have a chance to test this and comment on. I'm currently hitting a regression in 4.20-rc1 which causes it to not boot on my Cherry Trail test devices (sdhci driver times out so it cannot find its root filesystem). I'm currently debugging this (it looks like I need todo a full bisect to find the cause) once I've that working, if I hit something which look likes you've described I will give this patch a test. But currently I cannot reproduce the problem you describe. As for patches 2-55, they look good to me: Ackeed-by: Hans de Goede Regards, Hans