Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp1069770imm; Wed, 25 Jul 2018 10:58:10 -0700 (PDT) X-Google-Smtp-Source: AAOMgpdcrOkl2r9ebTeEJoX5s+wujAJpCtWHDNFd4o0a1l7l6kAXk/gaZJNqFEIg3Y/zDUdWOtiw X-Received: by 2002:a63:fb07:: with SMTP id o7-v6mr21823649pgh.333.1532541489945; Wed, 25 Jul 2018 10:58:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1532541489; cv=none; d=google.com; s=arc-20160816; b=pkDPnCP7iDO4mAgum37/sd/WENt6XQZ4HAgl4sNHo5vPh3g3PUj8X+nhzS1gNRcjxA Kjz8yDs6QAReuKfArAAtoApRa6cRkyb3Hscn2AH3U7d5YQ9C6m12QkjNiMMBNZEYCIGI yXeubuOJ7SgKJOLrHePb7Cl9f3PH7DeIbvlCjYgNi3PbkV3tJroSmlmekSN8G0Vyu8WO pnS5E1GmTHbbGEYXKlkBPFnlpWtrtU5dq+6QrlsEg0eURX2BmuYytGBv6LRFxahhY2RI IouHp/q+JkxmEzfrJuCtI9kEZySsEnTJA4uffySy5lsHS1sUqWt2qzok/rVvjREo/WUd lidg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:message-id:in-reply-to :subject:cc:to:from:date:arc-authentication-results; bh=2Th7Rka2wlOztL4/Y6CPbQGvCH8mNLCwK8IlhFOOskg=; b=REbZZyuUi7DmwOgutmjT7eN5QO3c3IbgDNY+jQWSd8SfytyxfAyzUgXoiw7q57vyET 30TlO0gz1fwSotqy6W6IXoFT0sq8gu6EYSxRoxcDFxX0gWpzNKXiqyDvT7K6TPnaZIGE jJERp396FAV76oxAouPRgY7h8NuXTIXs8cTtSWIQ9W/Z3QKcb96DTYOEBbWww7tJdcz2 lhbmamG83L1BT6FHvhniu7HC8b1F+39CNDKGJqMoBAHJtggEVmOIcUsHm1xSLMVcNvxG M0DIOHXG6nuQl3Ze3zFlTMTpBm6BM6U+Zstom7NGUj7HzDXvvL3jHkDmv/Bzd4HWrlNT AMEA== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id z15-v6si13996299pgf.293.2018.07.25.10.57.55; Wed, 25 Jul 2018 10:58:09 -0700 (PDT) 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730162AbeGYTJQ (ORCPT + 99 others); Wed, 25 Jul 2018 15:09:16 -0400 Received: from iolanthe.rowland.org ([192.131.102.54]:37386 "HELO iolanthe.rowland.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1729379AbeGYTJQ (ORCPT ); Wed, 25 Jul 2018 15:09:16 -0400 Received: (qmail 4865 invoked by uid 2102); 25 Jul 2018 13:56:32 -0400 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 25 Jul 2018 13:56:32 -0400 Date: Wed, 25 Jul 2018 13:56:32 -0400 (EDT) From: Alan Stern X-X-Sender: stern@iolanthe.rowland.org To: Kai-Heng Feng cc: arnd@arndb.de, , , , , , Subject: Re: [PATCH 2/5] memstick: Prevent memstick host from getting runtime suspended during card detection In-Reply-To: <20180725152515.1833-3-kai.heng.feng@canonical.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 25 Jul 2018, Kai-Heng Feng wrote: > We can use MEMSTICK_POWER_{ON,OFF} along with pm_runtime_{get,put} > helpers to let memstick host support runtime pm. > > There's a small window between memstick_detect_change() and its queued > work, memstick_check(). In this window the rpm count may go down to zero > before the memstick host powers on, so the host can be inadvertently > suspended. > > Increment rpm count before calling memstick_check(), and decrement rpm > count afterward, as now we are sure the memstick host should be > suspended or not. > > Signed-off-by: Kai-Heng Feng > --- > drivers/memstick/core/memstick.c | 4 ++++ > 1 file changed, 4 insertions(+) > > diff --git a/drivers/memstick/core/memstick.c b/drivers/memstick/core/memstick.c > index 76382c858c35..944fe0c93fa7 100644 > --- a/drivers/memstick/core/memstick.c > +++ b/drivers/memstick/core/memstick.c > @@ -18,6 +18,7 @@ > #include > #include > #include > +#include > > #define DRIVER_NAME "memstick" > > @@ -209,6 +210,7 @@ static int memstick_dummy_check(struct memstick_dev *card) > */ > void memstick_detect_change(struct memstick_host *host) > { > + pm_runtime_get_noresume(host->dev.parent); > queue_work(workqueue, &host->media_checker); > } > EXPORT_SYMBOL(memstick_detect_change); > @@ -479,6 +481,8 @@ static void memstick_check(struct work_struct *work) > host->set_param(host, MEMSTICK_POWER, MEMSTICK_POWER_OFF); > > mutex_unlock(&host->lock); > + > + pm_runtime_put_noidle(host->dev.parent); > dev_dbg(&host->dev, "memstick_check finished\n"); > } This should be pm_runtime_put(), not _put_noidle(). The reason is because if this call causes the PM runtime usage count to drop to 0, you do want the device to go into runtime suspend. Alan Stern