Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.31 as permitted sender) client-ip=23.128.96.31;
Date:   Wed, 25 Oct 2023 09:55:28 -0300
From:   Jason Gunthorpe <jgg@nvidia.com>
To:     Robin Murphy <robin.murphy@arm.com>
Cc:     joro@8bytes.org, will@kernel.org, iommu@lists.linux.dev,
        baolu.lu@linux.intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 3/7] iommu: Validate that devices match domains
Message-ID: <20231025125528.GG3952@nvidia.com>
References: <cover.1697047261.git.robin.murphy@arm.com>
 <4e8bda33aac4021b444e40389648deccf61c1f37.1697047261.git.robin.murphy@arm.com>
 <20231024185213.GA1061115@nvidia.com>
 <ec86712a-0c46-4b27-9736-e34b02168e19@arm.com>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <ec86712a-0c46-4b27-9736-e34b02168e19@arm.com>
MIME-Version: 1.0
X-MS-Exchange-AntiSpam-MessageData-ChunkCount: 1
X-MS-Exchange-AntiSpam-MessageData-0: =?us-ascii?Q?orLNzAPdXwa2dPbzYzrKkSYFYBt0gwLOlj0GpXjVMAV6RzVGRiqBNCvvos/0?=
 =?us-ascii?Q?UY/pvOdraH3MF6gDzMCv0sS5Q5I05Q1YT0tk3FPbxV4Lb7xWRocdL5Et/LAM?=
 =?us-ascii?Q?KgrbB+TG1nwlDPlVzvgNezSalwmmaYKGFeQU5l7nz8iyvzjpQ0ZScpyvItgv?=
 =?us-ascii?Q?Zs0bwBhqZe4MGaXJhvqud3Ni9BGmW0Nxum5GhhqCajwZ4bnRk/MbcM7zrbPG?=
 =?us-ascii?Q?iH7IMoSyJHRKHXiIgNpK9Br0bYt8F6RPavq4bbCG6eG6GVPZbpqg14nnnAPu?=
 =?us-ascii?Q?pYPCFF9wGNYVz2QW3gHgAphqtctJ9dtA+HSV6rC905fVvdDjNwsv38q6K6QY?=
 =?us-ascii?Q?zfa44eJTn7LT5lwQu/QiwRoYD47k2wWaEQQEN6FDxTTyI60/ECX7tRHaJxe5?=
 =?us-ascii?Q?5st4DTipcrjJLObkysONQHmCqWbhfkt0x9KTA8CCdMMHIdRCi31kgzbu1u2I?=
 =?us-ascii?Q?DzX3/GniDMxLfbHa0feAuAr+TcyRYt4vG06HrioIEj5ccJ+7rMpDhKDdPSuF?=
 =?us-ascii?Q?TaAg4VaIOnT+CEBAUBG3dWqjg3ye2lUUBdJcE7eDNum71OcEUohSLWBoG8j5?=
 =?us-ascii?Q?FjaB5P3tqmmlE1ZMu1Cy3mQn+E0GUZ+AhpFwyS+uPw2R/FEpFfHTkc8DpR4J?=
 =?us-ascii?Q?o7vaBaeveNQQwpAHeOQwm12nwLQLzTfpg5fF5OVkCaZDMa2EzOIAPtKHEVPz?=
 =?us-ascii?Q?vE49aL+Peg2VqGSA86/HmyyWvSIy12kvoex9OO1ok+j6fhSiW2hYJkmk4gSE?=
 =?us-ascii?Q?SqstQh3rnbolkznCpXOWg5C4nCFZiXIhFlGW6x1tBvkRZj8O64OTIyBeuyz3?=
 =?us-ascii?Q?PDwH24VGZR20+5FNnzfrasl4gxKSAkYP+Mi1W3H3rUTmAz4hmme4CuPH3TK9?=
 =?us-ascii?Q?jjFt4KdP0VWyALSPU9w6lzc4dUNtAnt/YKnVaO5C3hezd0GPAWL6mgQ4nIce?=
 =?us-ascii?Q?6nYOUZ3Nm05NejSNVpKA8jx3kqs/+znGOs3L1LxZYD3F4URRga/gulGCQ5MB?=
 =?us-ascii?Q?rgOI+jsRpGnpzaI4T1TNV+bmNJNAJNIvv/qfTB1rT2jku1aNTAFK4LUgixty?=
 =?us-ascii?Q?aPTN7c9cFbH4gYBfHrwFAdA48Jy5bKMShC6Wm7rUzbUWHeNBqM0cETSJ6aXp?=
 =?us-ascii?Q?RvjDppe20ddE9cZoAfoBwBWYvWJOCoaPGMkRbkKLu90k4eBJWhJNLWIA1Ozs?=
 =?us-ascii?Q?7iFvI0PuE+q/ruiQnfi4wZZRr1VKVNrNnaXqoVva7tcvhOpMG9v9QveXUbpT?=
 =?us-ascii?Q?orMCAEIXI41lIiDlVdyjOZhmEt/oGYbmLL5VEh8CS+jbdaOHFc8wE11fyRwK?=
 =?us-ascii?Q?o+mCw9P5MryujT+LJbeAVn5rLweUpX62cxa6suHLW8xOoAY0PZCfjy+lAUYA?=
 =?us-ascii?Q?IxISoGAXOSXKlkJHY2o+2e6NjFqCGEcEzXpEntjN/lgCbnmignFrOlzGqBMc?=
 =?us-ascii?Q?jsY7MG6WFYWOUM7TBwLJVXOVvqbTcGf85i5CpyTY5krX3NbL613tYE47rdhj?=
 =?us-ascii?Q?GOng5QO0gyMLi8vZPJc1KPCVccLTs/TNUfbNktvzm1weQppmwxS3cryNh1y3?=
 =?us-ascii?Q?CA5tJNjmD8s4XXxA5H9oEUkQV5+2IQtnRKrZSsxJ?=
X-OriginatorOrg: Nvidia.com
X-MS-Exchange-CrossTenant-Network-Message-Id: b3e7fbdc-5a4d-4219-1894-08dbd559aae0
X-MS-Exchange-CrossTenant-AuthSource: LV2PR12MB5869.namprd12.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 25 Oct 2023 12:55:29.9750
 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 43083d15-7273-40c1-b7db-39efd9ccc17a
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: 4ZyAziy+kccTDbqDbtsjsy580x9bGROxEF2u0aGBvLic4f8uhkAGrJjzIr5Fw9QG
X-MS-Exchange-Transport-CrossTenantHeadersStamped: IA1PR12MB7519
X-Spam-Status: No, score=-0.9 required=5.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,
	MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=unavailable
	autolearn_force=no version=3.4.6
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on morse.vger.email
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (morse.vger.email [0.0.0.0]); Wed, 25 Oct 2023 05:55:49 -0700 (PDT)

On Wed, Oct 25, 2023 at 01:39:56PM +0100, Robin Murphy wrote:
> On 24/10/2023 7:52 pm, Jason Gunthorpe wrote:
> > On Wed, Oct 11, 2023 at 07:14:50PM +0100, Robin Murphy wrote:
> > 
> > > @@ -2279,10 +2280,16 @@ struct iommu_domain *iommu_get_dma_domain(struct device *dev)
> > >   static int __iommu_attach_group(struct iommu_domain *domain,
> > >   				struct iommu_group *group)
> > >   {
> > > +	struct device *dev;
> > > +
> > >   	if (group->domain && group->domain != group->default_domain &&
> > >   	    group->domain != group->blocking_domain)
> > >   		return -EBUSY;
> > > +	dev = iommu_group_first_dev(group);
> > > +	if (!dev_has_iommu(dev) || dev_iommu_ops(dev) != domain->owner)
> > > +		return -EINVAL;
> > 
> > I was thinking about this later, how does this work for the global
> > static domains? domain->owner will not be set?
> > 
> > 	if (alloc_type == IOMMU_DOMAIN_IDENTITY && ops->identity_domain)
> > 		return ops->identity_domain;
> > 	else if (alloc_type == IOMMU_DOMAIN_BLOCKED && ops->blocked_domain)
> > 		return ops->blocked_domain;
> > 
> > Seems like it will break everything?
> 
> I don't believe it makes any significant difference - as the commit message
> points out, this validation is only applied at the public interface
> boundaries of iommu_attach_group(), iommu_attach_device(), 

Oh, making it only work for on domain type seems kind of hacky..

If that is the intention maybe the owner set should be moved into
iommu_domain_alloc() with a little comment noting that it is limited
to work in only a few cases?

I certainly didn't understand from the commit message to mean it was
only actually working for one domain type and this also blocks using
other types with the public interface.

> and iommu_attach_device_pasid(), which are only expected to be
> operating on explicitly-allocated unmanaged domains.

We have nesting now in the iommufd branch, and SVA will come soon for
these APIs.

Regardless this will clash with the iommufd branch for this reason so
I guess it needs to wait till rc1.

Thanks,
Jason