Received: by 2002:a05:7412:8d10:b0:f3:1519:9f41 with SMTP id bj16csp4431507rdb; Mon, 11 Dec 2023 21:28:21 -0800 (PST) X-Google-Smtp-Source: AGHT+IGE66uKQbRnl2PMYSkhp1ek9kbu4gi+a0cAf1/D5egmKTysoLyvYJA86cCE5K1Sp9HP1W0N X-Received: by 2002:a05:6808:6409:b0:3ba:108e:9127 with SMTP id fg9-20020a056808640900b003ba108e9127mr2389050oib.114.1702358901052; Mon, 11 Dec 2023 21:28:21 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1702358901; cv=none; d=google.com; s=arc-20160816; b=lRfNdARoUZhBLu9X6ocPbHwCFmV2rL9/BP2v+CWIQq3zdrwpmITTFL3geQFBnQsIIb 6paU0mRP0DSu4h6t7ocYf4vFtDaJIxDBLbhKGq6x7NcKnuaA+adeIRS2rRkawSC297go cOuNwCNlkur3vx90JGEV2PWCSE3k1FeYqK+VsvNiasfS0yio1nmHCtS46rqV6U1UnRud jLAOnE4rcPhsRZNqAU+qQ5FzUUc4/0hh28jyMKKPyrTA/uPj3Uiuc/3pwICR/5/jimT7 Z25P+lljfMcD+k9hD9gw4987C0Z6QYOTC2OdxCwDrGyGb0jDcCPAfhV5uBEIvkF/RTwX HV4g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:to:content-language:subject:cc:user-agent:mime-version :date:message-id:dkim-signature; bh=Of9UtB4ldc1V3vP67Zt66kO9ciX9UeIY63YI2DWiqq4=; fh=uzznn7J+IYAjVbPHItJO5zuzOqyiZAy1PaNe6S3d3bk=; b=jsgTmIFkSdR/+5toNhCzr+SdmrdgHa3Od6naOMx/Azao+/Tm0u3KjjoDl62tj9iGLd E9rjGAxW9yBsqLiDf5vA/kEmS/D89DMTvZTYhxnoLuEk7YyT8iswq6TXN8RNp122vE9z 3wTuif/iEpbdvG1nV3APTMEiVIDuxTv0JPJc6rTTbFM7QrjfLadQ0JT67y6WtcnAp2w2 S03NpP6Rd+w0wBLTc5LAVQHfBxwzgUCiZNfTjC2rW+mAYj16BSBTBsqQSM5vNWyNUYF+ cgDM+IdH1hEwaWaAhgkNro0PKwovqwhHkcA5cq/ZthYX1tyNJX9Fnn37EwlmBe4BMb43 hQKg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=gEBhMSHc; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.38 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from fry.vger.email (fry.vger.email. [23.128.96.38]) by mx.google.com with ESMTPS id s17-20020a632c11000000b005c212ebb55csi7224096pgs.691.2023.12.11.21.28.20 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 11 Dec 2023 21:28:21 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.38 as permitted sender) client-ip=23.128.96.38; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=gEBhMSHc; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.38 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by fry.vger.email (Postfix) with ESMTP id BC2CA809FA55; Mon, 11 Dec 2023 21:28:18 -0800 (PST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.11 at fry.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229537AbjLLF2G (ORCPT + 99 others); Tue, 12 Dec 2023 00:28:06 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37762 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229460AbjLLF2F (ORCPT ); Tue, 12 Dec 2023 00:28:05 -0500 Received: from mgamail.intel.com (mgamail.intel.com [192.55.52.120]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B9790A2; Mon, 11 Dec 2023 21:28:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1702358891; x=1733894891; h=message-id:date:mime-version:cc:subject:to:references: from:in-reply-to:content-transfer-encoding; bh=LCn4/xvODPorX9mTjeGLTue7GovKBlpADEjiJxDVln0=; b=gEBhMSHcFEskrkVLKBhzyoQ267f3votmpnQDy6DEj2U23I1T2Fv6LJ/A Cj0COUBJxY6RujJ4NZIQGo9lGpsJXdzm3EeMAU5XSiWJfHfqgSnMtdZWL 843Y3GJZJ0kP8xsi74ijF8WoVoo+bCwH6Auh9LjjAbh7cgcApk78Zm11W FmcHShbZbIEK006s3BxcdCekX0CACl0O5yjK3mnmZBSTBnKydZvtqlxwd nDsvE07lnTllTUQLhU8UxilOS/3O6GA+UIK8TYtQIvDy424Fe0yljPJOF H6J+UBp3pkvHtsx5o4Xh33V446krrGWyKOhSKOgrIec4i2UL9ZNZV7NHf Q==; X-IronPort-AV: E=McAfee;i="6600,9927,10921"; a="393626925" X-IronPort-AV: E=Sophos;i="6.04,269,1695711600"; d="scan'208";a="393626925" Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga104.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 11 Dec 2023 21:28:11 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10921"; a="807612687" X-IronPort-AV: E=Sophos;i="6.04,269,1695711600"; d="scan'208";a="807612687" Received: from allen-box.sh.intel.com (HELO [10.239.159.127]) ([10.239.159.127]) by orsmga001.jf.intel.com with ESMTP; 11 Dec 2023 21:28:07 -0800 Message-ID: Date: Tue, 12 Dec 2023 13:23:28 +0800 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Cc: baolu.lu@linux.intel.com, Joerg Roedel , Will Deacon , Robin Murphy , Kevin Tian , Jean-Philippe Brucker , Nicolin Chen , Yi Liu , Jacob Pan , Longfang Liu , Yan Zhao , iommu@lists.linux.dev, kvm@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v8 12/12] iommu: Use refcount for fault data access Content-Language: en-US To: Jason Gunthorpe References: <20231207064308.313316-1-baolu.lu@linux.intel.com> <20231207064308.313316-13-baolu.lu@linux.intel.com> <20231211152456.GB1489931@ziepe.ca> From: Baolu Lu In-Reply-To: <20231211152456.GB1489931@ziepe.ca> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on fry.vger.email Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (fry.vger.email [0.0.0.0]); Mon, 11 Dec 2023 21:28:19 -0800 (PST) On 12/11/23 11:24 PM, Jason Gunthorpe wrote: >> @@ -282,22 +313,15 @@ EXPORT_SYMBOL_GPL(iommu_page_response); >> */ >> int iopf_queue_flush_dev(struct device *dev) >> { >> - int ret = 0; >> - struct iommu_fault_param *iopf_param; >> - struct dev_iommu *param = dev->iommu; >> + struct iommu_fault_param *iopf_param = iopf_get_dev_fault_param(dev); >> >> - if (!param) >> + if (!iopf_param) >> return -ENODEV; > And this also seems unnecessary, it is a bug to call this after > iopf_queue_remove_device() right? Just Yes. They both are called from the iommu driver. The iommu driver should guarantee this. > rcu_derefernce(param->fault_param, true) and WARN_ON NULL. Okay, sure. Best regards, baolu