Received: by 2002:ac0:bc90:0:0:0:0:0 with SMTP id a16csp3146530img; Mon, 25 Mar 2019 04:51:33 -0700 (PDT) X-Google-Smtp-Source: APXvYqwMqHIFiZILNCcHfVQCxqyLhBpQLhcPVJuU+VQXYKjk+gNVfScNn8VwbU5/6vHrWNVVRbr1 X-Received: by 2002:a17:902:9683:: with SMTP id n3mr25044020plp.333.1553514693801; Mon, 25 Mar 2019 04:51:33 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1553514693; cv=none; d=google.com; s=arc-20160816; b=K2LY9Y1YVX+jUUqmABFErWFloXb5Da1f2dOrGofUNMDsPILZsKfbhH18gBILHvtnwp RUdgJIKsQ4AEDUCX6zTvdJ2pOtf+ps/y/Ma0PRipUctEVM0rD58Ynz8RqyAboV5F1M/C To3r5IbW6qTMV28LIezcLcu4R1F+xCgigQqwy9EomJmSyFkpvKWeTR8dtJVWHE/DAXrf TZqlu4mUnqQhMe/xcRUXWX16vOI3mz8y5UwK/WDL0SiEDmWzpFhnISdc2Wbuj4GIWVga u/NU4zD4mK/wS9Om9u7EvxoHc5eKLLtFUafnwS0rnoPWJ5iAymV7fgQ64WflQSjifT1k doXw== 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:mime-version :references:in-reply-to:date:to:from:subject:message-id; bh=7gRXM+FFeb8RrlkdUgDT8OlxQDK6gNu1lB7bamL1eBI=; b=cfT/80TxrzOFJlNserbWtZssP6F8HrIQ/3YN6QFKgziWAk3qEinbpt1lRfTD62mhEw XuZu2Uf06L4rshcTps3u4VMCvdfO/3hCPWnssv0hDE2HkWmIt6dPwEsgeT8oBvF/gLTJ A3lXD4uNwhs0H331RSRu5XSzAKvyZn/CQJGjjNsDgv8zYnM72hm31PncLsjoz6VOEPAt H8uGaGrf2QhrGVV+HlfIH/V8/iEBTds/F7z16JVGQgxpHT5EyFz6iLcOru02EWTj/nOL MiSJ3iUvjFMjvVqDSK2+WwEISpkzNVOFFH4MmpUoE5JWix46FAd/0lOo0HLQlffhdz3L sTpw== 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 j65si8891578pge.48.2019.03.25.04.51.18; Mon, 25 Mar 2019 04:51:33 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730958AbfCYLs5 (ORCPT + 99 others); Mon, 25 Mar 2019 07:48:57 -0400 Received: from mx1.redhat.com ([209.132.183.28]:40478 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729831AbfCYLs4 (ORCPT ); Mon, 25 Mar 2019 07:48:56 -0400 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id B197C3099FD1; Mon, 25 Mar 2019 11:48:56 +0000 (UTC) Received: from maximlenovopc.usersys.redhat.com (unknown [10.35.206.72]) by smtp.corp.redhat.com (Postfix) with ESMTP id 1D55576F62; Mon, 25 Mar 2019 11:48:52 +0000 (UTC) Message-ID: Subject: Re: [PATCH 1/8] vfio/mdev: Fix to not do put_device on device_register failure From: Maxim Levitsky To: Parav Pandit , kvm@vger.kernel.org, linux-kernel@vger.kernel.org, kwankhede@nvidia.com, alex.williamson@redhat.com Date: Mon, 25 Mar 2019 13:48:51 +0200 In-Reply-To: <1553296835-37522-2-git-send-email-parav@mellanox.com> References: <1553296835-37522-1-git-send-email-parav@mellanox.com> <1553296835-37522-2-git-send-email-parav@mellanox.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.41]); Mon, 25 Mar 2019 11:48:56 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2019-03-22 at 18:20 -0500, Parav Pandit wrote: > device_register() performs put_device() if device_add() fails. > This balances with device_initialize(). > > mdev core performing put_device() when device_register() fails, > is an error that puts already released device again. > Therefore, don't put the device on error. > > Fixes: 7b96953bc640 ("vfio: Mediated device Core driver") > Signed-off-by: Parav Pandit > --- > drivers/vfio/mdev/mdev_core.c | 4 +--- > 1 file changed, 1 insertion(+), 3 deletions(-) > > diff --git a/drivers/vfio/mdev/mdev_core.c b/drivers/vfio/mdev/mdev_core.c > index 0212f0e..3e5880a 100644 > --- a/drivers/vfio/mdev/mdev_core.c > +++ b/drivers/vfio/mdev/mdev_core.c > @@ -318,10 +318,8 @@ int mdev_device_create(struct kobject *kobj, struct > device *dev, uuid_le uuid) > dev_set_name(&mdev->dev, "%pUl", uuid.b); > > ret = device_register(&mdev->dev); > - if (ret) { > - put_device(&mdev->dev); > + if (ret) > goto mdev_fail; > - } > > ret = mdev_device_create_ops(kobj, mdev); > if (ret) Very good catch! Thanks! Reviewed-by: Maxim Levitsky Best regards, Maxim Levitsky