From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5D4D7C282CE for ; Tue, 12 Feb 2019 12:11:03 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 367F220821 for ; Tue, 12 Feb 2019 12:11:03 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729377AbfBLMLB (ORCPT ); Tue, 12 Feb 2019 07:11:01 -0500 Received: from cloudserver094114.home.pl ([79.96.170.134]:42647 "EHLO cloudserver094114.home.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728059AbfBLMK5 (ORCPT ); Tue, 12 Feb 2019 07:10:57 -0500 Received: from 79.184.254.36.ipv4.supernova.orange.pl (79.184.254.36) (HELO aspire.rjw.lan) by serwer1319399.home.pl (79.96.170.134) with SMTP (IdeaSmtpServer 0.83.183) id c310edeb91d99401; Tue, 12 Feb 2019 13:10:55 +0100 From: "Rafael J. Wysocki" To: Greg Kroah-Hartman Cc: LKML , Linux PM , Ulf Hansson , Daniel Vetter , Lukas Wunner , Andrzej Hajda , Russell King - ARM Linux , Lucas Stach , Linus Walleij , Thierry Reding , Laurent Pinchart , Marek Szyprowski Subject: [PATCH 0/2] driver core: Fixes related to device links Date: Tue, 12 Feb 2019 13:01:13 +0100 Message-ID: <5510642.nRbR3bcduN@aspire.rjw.lan> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit 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 Hi Greg at al, These fix two issues on top of the recent device links material in driver-core/driver-core-next. The first one fixes a race condition that may trigger when __pm_runtime_set_status() is used incorrectly (that is, when it is called with PM-runtime enabled for the target device and working). The second one fixes a supplier PM-runtime usage counter imbalance resulting from adding and removing (e.g. in the error code path) a stateless device link to it from within the consumer driver's probe callback. Please refer to the patch changelogs for details. Cheers, Rafael