mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hans Verkuil <hverkuil-cisco@xs4all.nl>
To: "Yunfei Dong" <yunfei.dong@mediatek.com>,
	"Jeffrey Kardatzke" <jkardatzke@google.com>,
	"Nícolas F . R . A . Prado" <nfraprado@collabora.com>,
	"Nicolas Dufresne" <nicolas.dufresne@collabora.com>,
	"AngeloGioacchino Del Regno"
	<angelogioacchino.delregno@collabora.com>,
	"Benjamin Gaignard" <benjamin.gaignard@collabora.com>,
	"Nathan Hebert" <nhebert@chromium.org>
Cc: "Chen-Yu Tsai" <wenst@chromium.org>,
	"Yong Wu" <yong.wu@mediatek.com>,
	"Hsin-Yi Wang" <hsinyi@chromium.org>,
	"Fritz Koenig" <frkoenig@chromium.org>,
	"Daniel Vetter" <daniel@ffwll.ch>,
	"Steve Cho" <stevecho@chromium.org>,
	"Sumit Semwal" <sumit.semwal@linaro.org>,
	"Brian Starkey" <Brian.Starkey@arm.com>,
	"John Stultz" <jstultz@google.com>,
	"T . J . Mercier" <tjmercier@google.com>,
	"Christian König" <christian.koenig@amd.com>,
	"Matthias Brugger" <matthias.bgg@gmail.com>,
	dri-devel@lists.freedesktop.org, linaro-mm-sig@lists.linaro.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org,
	Project_Global_Chrome_Upstream_Group@mediatek.com
Subject: Re: [PATCH v3,03/21] v4l2: verify secure dmabufs are used in secure queue
Date: Mon, 11 Dec 2023 11:58:36 +0100	[thread overview]
Message-ID: <705ce6b0-e945-404c-8014-38881a01fbca@xs4all.nl> (raw)
In-Reply-To: <20231206081538.17056-4-yunfei.dong@mediatek.com>

On 06/12/2023 09:15, Yunfei Dong wrote:
> From: Jeffrey Kardatzke <jkardatzke@google.com>
> 
> Verfies in the dmabuf implementations that if the secure memory flag is

Verfies -> Verifies

> set for a queue that the dmabuf submitted to the queue is unmappable.
> 
> Signed-off-by: Jeffrey Kardatzke <jkardatzke@google.com>
> Signed-off-by: Yunfei Dong <yunfei.dong@mediatek.com>
> ---
>  drivers/media/common/videobuf2/videobuf2-dma-contig.c | 6 ++++++
>  drivers/media/common/videobuf2/videobuf2-dma-sg.c     | 6 ++++++
>  2 files changed, 12 insertions(+)
> 
> diff --git a/drivers/media/common/videobuf2/videobuf2-dma-contig.c b/drivers/media/common/videobuf2/videobuf2-dma-contig.c
> index 3d4fd4ef5310..ad58ef8dc231 100644
> --- a/drivers/media/common/videobuf2/videobuf2-dma-contig.c
> +++ b/drivers/media/common/videobuf2/videobuf2-dma-contig.c
> @@ -710,6 +710,12 @@ static int vb2_dc_map_dmabuf(void *mem_priv)
>  		return -EINVAL;
>  	}
>  
> +	/* verify the dmabuf is secure if we are in secure mode */
> +	if (buf->vb->vb2_queue->secure_mem && sg_page(sgt->sgl)) {

This needs a bit more explanation. I guess that for secure memory
sg_page returns NULL?

> +		pr_err("secure queue requires secure dma_buf");
> +		return -EINVAL;
> +	}
> +
>  	/* checking if dmabuf is big enough to store contiguous chunk */
>  	contig_size = vb2_dc_get_contiguous_size(sgt);
>  	if (contig_size < buf->size) {
> diff --git a/drivers/media/common/videobuf2/videobuf2-dma-sg.c b/drivers/media/common/videobuf2/videobuf2-dma-sg.c
> index 28f3fdfe23a2..55428c73c380 100644
> --- a/drivers/media/common/videobuf2/videobuf2-dma-sg.c
> +++ b/drivers/media/common/videobuf2/videobuf2-dma-sg.c
> @@ -564,6 +564,12 @@ static int vb2_dma_sg_map_dmabuf(void *mem_priv)
>  		return -EINVAL;
>  	}
>  
> +	/* verify the dmabuf is secure if we are in secure mode */
> +	if (buf->vb->vb2_queue->secure_mem && !sg_dma_secure(sgt->sgl)) {

I can't find the sg_dma_secure function. I suspect this patch series
depends on another series?

> +		pr_err("secure queue requires secure dma_buf");
> +		return -EINVAL;
> +	}
> +
>  	buf->dma_sgt = sgt;
>  	buf->vaddr = NULL;
>  

Regards,

	Hans

  reply	other threads:[~2023-12-11 10:58 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-06  8:15 [PATCH v3,00/21] add driver to support secure video decoder Yunfei Dong
2023-12-06  8:15 ` [PATCH v3,01/21] v4l2: add secure memory flags Yunfei Dong
2023-12-06  8:15 ` [PATCH v3,02/21] v4l2: handle secure memory flags in queue setup Yunfei Dong
2023-12-11 10:45   ` Hans Verkuil
2024-01-04 20:04     ` Jeffrey Kardatzke
2023-12-06  8:15 ` [PATCH v3,03/21] v4l2: verify secure dmabufs are used in secure queue Yunfei Dong
2023-12-11 10:58   ` Hans Verkuil [this message]
2024-01-04 20:07     ` Jeffrey Kardatzke
2023-12-06  8:15 ` [PATCH v3,04/21] v4l: add documentation for secure memory flag Yunfei Dong
2023-12-11 11:05   ` Hans Verkuil
2024-01-04 20:05     ` Jeffrey Kardatzke
2024-01-08  8:29       ` Hans Verkuil
2024-01-17 20:02   ` Nicolas Dufresne
2023-12-06  8:15 ` [PATCH v3,05/21] dma-buf: heaps: Deduplicate docs and adopt common format Yunfei Dong
2023-12-06  8:15 ` [PATCH v3,06/21] dma-heap: Add proper kref handling on dma-buf heaps Yunfei Dong
2023-12-06  8:15 ` [PATCH v3,07/21] dma-heap: Provide accessors so that in-kernel drivers can allocate dmabufs from specific heaps Yunfei Dong
2023-12-06  8:15 ` [PATCH v3,08/21] media: mediatek: vcodec: add tee client interface to communiate with optee-os Yunfei Dong
2023-12-06  8:15 ` [PATCH v3,09/21] media: mediatek: vcodec: allocate tee share memory Yunfei Dong
2023-12-06  8:15 ` [PATCH v3,10/21] media: mediatek: vcodec: send share memory data to optee Yunfei Dong
2023-12-06  8:15 ` [PATCH v3,11/21] media: mediatek: vcodec: initialize msg and vsi information Yunfei Dong
2023-12-06  8:15 ` [PATCH v3,12/21] media: mediatek: vcodec: add interface to allocate/free secure memory Yunfei Dong
2023-12-06  8:15 ` [PATCH v3,13/21] media: mediatek: vcodec: using shared memory as vsi address Yunfei Dong
2023-12-06  8:15 ` [PATCH v3,14/21] media: mediatek: vcodec: Add capture format to support one plane memory Yunfei Dong
2023-12-06  8:15 ` [PATCH v3,15/21] media: mediatek: vcodec: Add one plane format Yunfei Dong
2023-12-06  8:15 ` [PATCH v3,16/21] media: medkatek: vcodec: support one plane capture buffer Yunfei Dong
2023-12-06  8:46   ` Hans Verkuil
2023-12-06  8:15 ` [PATCH v3,17/21] media: medkatek: vcodec: re-construct h264 driver to support svp mode Yunfei Dong
2023-12-06  8:15 ` [PATCH v3,18/21] media: medkatek: vcodec: remove parse nal_info in kernel Yunfei Dong
2023-12-06  8:15 ` [PATCH v3,19/21] media: medkatek: vcodec: disable wait interrupt for svp mode Yunfei Dong
2023-12-06  8:15 ` [PATCH v3,20/21] media: medkatek: vcodec: support tee decoder Yunfei Dong
2023-12-06 23:43   ` [PATCH] " kernel test robot
2023-12-06 23:43   ` kernel test robot
2023-12-06  8:15 ` [PATCH v3,21/21] media: mediatek: vcodec: move vdec init interface to setup callback Yunfei Dong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=705ce6b0-e945-404c-8014-38881a01fbca@xs4all.nl \
    --to=hverkuil-cisco@xs4all.nl \
    --cc=Brian.Starkey@arm.com \
    --cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=benjamin.gaignard@collabora.com \
    --cc=christian.koenig@amd.com \
    --cc=daniel@ffwll.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=frkoenig@chromium.org \
    --cc=hsinyi@chromium.org \
    --cc=jkardatzke@google.com \
    --cc=jstultz@google.com \
    --cc=linaro-mm-sig@lists.linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=nfraprado@collabora.com \
    --cc=nhebert@chromium.org \
    --cc=nicolas.dufresne@collabora.com \
    --cc=stevecho@chromium.org \
    --cc=sumit.semwal@linaro.org \
    --cc=tjmercier@google.com \
    --cc=wenst@chromium.org \
    --cc=yong.wu@mediatek.com \
    --cc=yunfei.dong@mediatek.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®