On 02/05/2025 10:59 am, Jens Wiklander wrote:
If a parent device is supplied to tee_device_alloc(), copy the dma_mask field into the new device. This avoids future warnings when mapping a DMA-buf for the device.
That also sounds dodgy. If the parent device is the hardware device physically performing the DMA, then that is the device which should be passed to the DMA API. Trying to copy random bits of one device's configuration to another device and hoping it will work is not robust - not only is DMA-relevant information all over the place, including in archdata and/or bus/IOMMU driver-private data, but it can also opens up a whole can of subtle lifecycle issues...
Signed-off-by: Jens Wiklander jens.wiklander@linaro.org Reviewed-by: Sumit Garg sumit.garg@kernel.org
drivers/tee/tee_core.c | 2 ++ 1 file changed, 2 insertions(+)
diff --git a/drivers/tee/tee_core.c b/drivers/tee/tee_core.c index d113679b1e2d..685afcaa3ea1 100644 --- a/drivers/tee/tee_core.c +++ b/drivers/tee/tee_core.c @@ -922,6 +922,8 @@ struct tee_device *tee_device_alloc(const struct tee_desc *teedesc, teedev->dev.class = &tee_class; teedev->dev.release = tee_release_device; teedev->dev.parent = dev;
- if (dev)
teedev->dev.dma_mask = dev->dma_mask;
...for instance, I don't see any obvious guarantee that "dev" can't go away during the lifetime of "teedev" and leave this pointer dangling.
Thanks, Robin.
teedev->dev.devt = MKDEV(MAJOR(tee_devt), teedev->id);