From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: "Andrew F. Davis" <afd@ti.com>, Sumit Semwal <sumit.semwal@linaro.org>
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] dma-buf: Make mmap callback actually optional
Date: Mon, 1 Apr 2019 15:38:36 +0200 [thread overview]
Message-ID: <24aa0897-8f23-f747-d9a4-d5272f37beea@gmail.com> (raw)
In-Reply-To: <20190329165201.16233-1-afd@ti.com>
Am 29.03.19 um 17:52 schrieb Andrew F. Davis:
> The docs state the callback is optional but it is not, make it optional.
>
> Signed-off-by: Andrew F. Davis <afd@ti.com>
Reviewed-by: Christian König <christian.koenig@amd.com>
> ---
> drivers/dma-buf/dma-buf.c | 11 +++++++++--
> 1 file changed, 9 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/dma-buf/dma-buf.c b/drivers/dma-buf/dma-buf.c
> index 7c858020d14b..4d4ae9fe9ac8 100644
> --- a/drivers/dma-buf/dma-buf.c
> +++ b/drivers/dma-buf/dma-buf.c
> @@ -90,6 +90,10 @@ static int dma_buf_mmap_internal(struct file *file, struct vm_area_struct *vma)
>
> dmabuf = file->private_data;
>
> + /* check if buffer supports mmap */
> + if (!dmabuf->ops->mmap)
> + return -EINVAL;
> +
> /* check for overflowing the buffer's size */
> if (vma->vm_pgoff + vma_pages(vma) >
> dmabuf->size >> PAGE_SHIFT)
> @@ -404,8 +408,7 @@ struct dma_buf *dma_buf_export(const struct dma_buf_export_info *exp_info)
> || !exp_info->ops
> || !exp_info->ops->map_dma_buf
> || !exp_info->ops->unmap_dma_buf
> - || !exp_info->ops->release
> - || !exp_info->ops->mmap)) {
> + || !exp_info->ops->release)) {
> return ERR_PTR(-EINVAL);
> }
>
> @@ -906,6 +909,10 @@ int dma_buf_mmap(struct dma_buf *dmabuf, struct vm_area_struct *vma,
> if (WARN_ON(!dmabuf || !vma))
> return -EINVAL;
>
> + /* check if buffer supports mmap */
> + if (!dmabuf->ops->mmap)
> + return -EINVAL;
> +
> /* check for offset overflow */
> if (pgoff + vma_pages(vma) < pgoff)
> return -EOVERFLOW;
next prev parent reply other threads:[~2019-04-01 13:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-29 16:52 Andrew F. Davis
2019-04-01 7:13 ` Daniel Vetter
2019-04-01 13:27 ` Andrew F. Davis
2019-04-01 13:38 ` Christian König [this message]
2019-04-03 6:30 ` Sumit Semwal
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=24aa0897-8f23-f747-d9a4-d5272f37beea@gmail.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=afd@ti.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sumit.semwal@linaro.org \
/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®