All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <christian.koenig@amd.com>
To: guangming.cao@mediatek.com
Cc: benjamin.gaignard@linaro.org, bo.song@mediatek.com,
	caoguangming34@gmail.com, dri-devel@lists.freedesktop.org,
	jianjiao.zeng@mediatek.com, john.stultz@linaro.org,
	labbott@redhat.com, libo.kang@mediatek.com,
	linaro-mm-sig@lists.linaro.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
	linux-mediatek@lists.infradead.org, lmark@codeaurora.org,
	matthias.bgg@gmail.com, michael.j.ruhl@intel.com,
	mingyuan.ma@mediatek.com, sumit.semwal@linaro.org,
	wsd_upstream@mediatek.com, yf.wang@mediatek.com
Subject: Re: [PATCH v6 RESEND] dma-buf: system_heap: Add a size check for allocation
Date: Thu, 20 Jan 2022 11:22:10 +0100	[thread overview]
Message-ID: <90bf495d-dbf6-cb0d-f54f-e0080b810f8d@amd.com> (raw)
In-Reply-To: <20220120100036.99867-1-guangming.cao@mediatek.com>

Am 20.01.22 um 11:00 schrieb guangming.cao@mediatek.com:
> From: Guangming <Guangming.Cao@mediatek.com>
>
> Add a size check for allocation since the allocation size should be
> always less than the total DRAM size on system heap.
> Adding this check can prevent comsuming too much time for invalid allocations.
>
> Signed-off-by: Guangming <Guangming.Cao@mediatek.com>
> Acked-by: John Stultz <john.stultz@linaro.org>

Acked-by: Christian König <christian.koenig@amd.com>

> ---
>   drivers/dma-buf/heaps/system_heap.c | 8 ++++++++
>   1 file changed, 8 insertions(+)
>
> diff --git a/drivers/dma-buf/heaps/system_heap.c b/drivers/dma-buf/heaps/system_heap.c
> index 23a7e74ef966..b65e597a742f 100644
> --- a/drivers/dma-buf/heaps/system_heap.c
> +++ b/drivers/dma-buf/heaps/system_heap.c
> @@ -347,6 +347,14 @@ static struct dma_buf *system_heap_allocate(struct dma_heap *heap,
>   	struct page *page, *tmp_page;
>   	int i, ret = -ENOMEM;
>   
> +	/*
> +	 * Size check. The "len" should be less than totalram since system_heap
> +	 * memory is comes from system. Adding check here can prevent comsuming
> +	 * too much time for invalid allocations.
> +	 */
> +	if (PFN_DOWN(len) > totalram_pages())
> +		return ERR_PTR(-EINVAL);
> +
>   	buffer = kzalloc(sizeof(*buffer), GFP_KERNEL);
>   	if (!buffer)
>   		return ERR_PTR(-ENOMEM);


WARNING: multiple messages have this Message-ID (diff)
From: "Christian König" <christian.koenig@amd.com>
To: guangming.cao@mediatek.com
Cc: benjamin.gaignard@linaro.org, bo.song@mediatek.com,
	caoguangming34@gmail.com, dri-devel@lists.freedesktop.org,
	jianjiao.zeng@mediatek.com, john.stultz@linaro.org,
	labbott@redhat.com, libo.kang@mediatek.com,
	linaro-mm-sig@lists.linaro.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
	linux-mediatek@lists.infradead.org, lmark@codeaurora.org,
	matthias.bgg@gmail.com, michael.j.ruhl@intel.com,
	mingyuan.ma@mediatek.com, sumit.semwal@linaro.org,
	wsd_upstream@mediatek.com, yf.wang@mediatek.com
Subject: Re: [PATCH v6 RESEND] dma-buf: system_heap: Add a size check for allocation
Date: Thu, 20 Jan 2022 11:22:10 +0100	[thread overview]
Message-ID: <90bf495d-dbf6-cb0d-f54f-e0080b810f8d@amd.com> (raw)
In-Reply-To: <20220120100036.99867-1-guangming.cao@mediatek.com>

Am 20.01.22 um 11:00 schrieb guangming.cao@mediatek.com:
> From: Guangming <Guangming.Cao@mediatek.com>
>
> Add a size check for allocation since the allocation size should be
> always less than the total DRAM size on system heap.
> Adding this check can prevent comsuming too much time for invalid allocations.
>
> Signed-off-by: Guangming <Guangming.Cao@mediatek.com>
> Acked-by: John Stultz <john.stultz@linaro.org>

Acked-by: Christian König <christian.koenig@amd.com>

> ---
>   drivers/dma-buf/heaps/system_heap.c | 8 ++++++++
>   1 file changed, 8 insertions(+)
>
> diff --git a/drivers/dma-buf/heaps/system_heap.c b/drivers/dma-buf/heaps/system_heap.c
> index 23a7e74ef966..b65e597a742f 100644
> --- a/drivers/dma-buf/heaps/system_heap.c
> +++ b/drivers/dma-buf/heaps/system_heap.c
> @@ -347,6 +347,14 @@ static struct dma_buf *system_heap_allocate(struct dma_heap *heap,
>   	struct page *page, *tmp_page;
>   	int i, ret = -ENOMEM;
>   
> +	/*
> +	 * Size check. The "len" should be less than totalram since system_heap
> +	 * memory is comes from system. Adding check here can prevent comsuming
> +	 * too much time for invalid allocations.
> +	 */
> +	if (PFN_DOWN(len) > totalram_pages())
> +		return ERR_PTR(-EINVAL);
> +
>   	buffer = kzalloc(sizeof(*buffer), GFP_KERNEL);
>   	if (!buffer)
>   		return ERR_PTR(-ENOMEM);


_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek

WARNING: multiple messages have this Message-ID (diff)
From: "Christian König" <christian.koenig@amd.com>
To: guangming.cao@mediatek.com
Cc: linux-arm-kernel@lists.infradead.org,
	linaro-mm-sig@lists.linaro.org, lmark@codeaurora.org,
	wsd_upstream@mediatek.com, linux-kernel@vger.kernel.org,
	dri-devel@lists.freedesktop.org, caoguangming34@gmail.com,
	michael.j.ruhl@intel.com, yf.wang@mediatek.com,
	libo.kang@mediatek.com, benjamin.gaignard@linaro.org,
	bo.song@mediatek.com, matthias.bgg@gmail.com,
	linux-mediatek@lists.infradead.org, labbott@redhat.com,
	mingyuan.ma@mediatek.com, jianjiao.zeng@mediatek.com,
	linux-media@vger.kernel.org
Subject: Re: [PATCH v6 RESEND] dma-buf: system_heap: Add a size check for allocation
Date: Thu, 20 Jan 2022 11:22:10 +0100	[thread overview]
Message-ID: <90bf495d-dbf6-cb0d-f54f-e0080b810f8d@amd.com> (raw)
In-Reply-To: <20220120100036.99867-1-guangming.cao@mediatek.com>

Am 20.01.22 um 11:00 schrieb guangming.cao@mediatek.com:
> From: Guangming <Guangming.Cao@mediatek.com>
>
> Add a size check for allocation since the allocation size should be
> always less than the total DRAM size on system heap.
> Adding this check can prevent comsuming too much time for invalid allocations.
>
> Signed-off-by: Guangming <Guangming.Cao@mediatek.com>
> Acked-by: John Stultz <john.stultz@linaro.org>

Acked-by: Christian König <christian.koenig@amd.com>

> ---
>   drivers/dma-buf/heaps/system_heap.c | 8 ++++++++
>   1 file changed, 8 insertions(+)
>
> diff --git a/drivers/dma-buf/heaps/system_heap.c b/drivers/dma-buf/heaps/system_heap.c
> index 23a7e74ef966..b65e597a742f 100644
> --- a/drivers/dma-buf/heaps/system_heap.c
> +++ b/drivers/dma-buf/heaps/system_heap.c
> @@ -347,6 +347,14 @@ static struct dma_buf *system_heap_allocate(struct dma_heap *heap,
>   	struct page *page, *tmp_page;
>   	int i, ret = -ENOMEM;
>   
> +	/*
> +	 * Size check. The "len" should be less than totalram since system_heap
> +	 * memory is comes from system. Adding check here can prevent comsuming
> +	 * too much time for invalid allocations.
> +	 */
> +	if (PFN_DOWN(len) > totalram_pages())
> +		return ERR_PTR(-EINVAL);
> +
>   	buffer = kzalloc(sizeof(*buffer), GFP_KERNEL);
>   	if (!buffer)
>   		return ERR_PTR(-ENOMEM);


WARNING: multiple messages have this Message-ID (diff)
From: "Christian König" <christian.koenig@amd.com>
To: guangming.cao@mediatek.com
Cc: benjamin.gaignard@linaro.org, bo.song@mediatek.com,
	caoguangming34@gmail.com, dri-devel@lists.freedesktop.org,
	jianjiao.zeng@mediatek.com, john.stultz@linaro.org,
	labbott@redhat.com, libo.kang@mediatek.com,
	linaro-mm-sig@lists.linaro.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
	linux-mediatek@lists.infradead.org, lmark@codeaurora.org,
	matthias.bgg@gmail.com, michael.j.ruhl@intel.com,
	mingyuan.ma@mediatek.com, sumit.semwal@linaro.org,
	wsd_upstream@mediatek.com, yf.wang@mediatek.com
Subject: Re: [PATCH v6 RESEND] dma-buf: system_heap: Add a size check for allocation
Date: Thu, 20 Jan 2022 11:22:10 +0100	[thread overview]
Message-ID: <90bf495d-dbf6-cb0d-f54f-e0080b810f8d@amd.com> (raw)
In-Reply-To: <20220120100036.99867-1-guangming.cao@mediatek.com>

Am 20.01.22 um 11:00 schrieb guangming.cao@mediatek.com:
> From: Guangming <Guangming.Cao@mediatek.com>
>
> Add a size check for allocation since the allocation size should be
> always less than the total DRAM size on system heap.
> Adding this check can prevent comsuming too much time for invalid allocations.
>
> Signed-off-by: Guangming <Guangming.Cao@mediatek.com>
> Acked-by: John Stultz <john.stultz@linaro.org>

Acked-by: Christian König <christian.koenig@amd.com>

> ---
>   drivers/dma-buf/heaps/system_heap.c | 8 ++++++++
>   1 file changed, 8 insertions(+)
>
> diff --git a/drivers/dma-buf/heaps/system_heap.c b/drivers/dma-buf/heaps/system_heap.c
> index 23a7e74ef966..b65e597a742f 100644
> --- a/drivers/dma-buf/heaps/system_heap.c
> +++ b/drivers/dma-buf/heaps/system_heap.c
> @@ -347,6 +347,14 @@ static struct dma_buf *system_heap_allocate(struct dma_heap *heap,
>   	struct page *page, *tmp_page;
>   	int i, ret = -ENOMEM;
>   
> +	/*
> +	 * Size check. The "len" should be less than totalram since system_heap
> +	 * memory is comes from system. Adding check here can prevent comsuming
> +	 * too much time for invalid allocations.
> +	 */
> +	if (PFN_DOWN(len) > totalram_pages())
> +		return ERR_PTR(-EINVAL);
> +
>   	buffer = kzalloc(sizeof(*buffer), GFP_KERNEL);
>   	if (!buffer)
>   		return ERR_PTR(-ENOMEM);


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-01-20 10:22 UTC|newest]

Thread overview: 93+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-17  9:41 [PATCH] dma-buf: dma-heap: Add a size limitation for allocation guangming.cao
2021-12-17  9:41 ` guangming.cao
2021-12-17  9:41 ` guangming.cao
2021-12-17  9:41 ` guangming.cao
2021-12-27  9:51 ` [PATCH v2] dma-buf: dma-heap: Add a size check " guangming.cao
2021-12-27  9:51   ` guangming.cao
2021-12-27  9:51   ` guangming.cao
2021-12-27  9:51   ` guangming.cao
2022-01-03 18:57   ` John Stultz
2022-01-03 18:57     ` John Stultz
2022-01-03 18:57     ` John Stultz
2022-01-03 18:57     ` John Stultz
2022-01-04  7:47     ` Christian König
2022-01-04  7:47       ` Christian König
2022-01-04  7:47       ` Christian König
2022-01-04  7:47       ` Christian König
2022-01-04  8:44       ` Guangming.Cao
2022-01-04  8:44         ` Guangming.Cao
2022-01-04  8:44         ` Guangming.Cao
2022-01-05  6:36       ` guangming.cao
2022-01-05  6:36         ` guangming.cao
2022-01-05  6:36         ` guangming.cao
2022-01-05  6:36         ` guangming.cao
2022-01-13 10:50         ` Sumit Semwal
2022-01-13 10:50           ` Sumit Semwal
2022-01-13 10:50           ` Sumit Semwal
2022-01-13 10:50           ` Sumit Semwal
2022-01-13 12:34           ` [PATCH v3] " guangming.cao
2022-01-13 12:34             ` guangming.cao
2022-01-13 12:34             ` guangming.cao
2022-01-13 12:34             ` guangming.cao
2022-01-13 12:57             ` Ruhl, Michael J
2022-01-13 12:57               ` Ruhl, Michael J
2022-01-13 12:57               ` Ruhl, Michael J
2022-01-13 12:57               ` Ruhl, Michael J
2022-01-13 13:00               ` Ruhl, Michael J
2022-01-13 13:00                 ` Ruhl, Michael J
2022-01-13 13:00                 ` Ruhl, Michael J
2022-01-13 13:00                 ` Ruhl, Michael J
2022-01-13 13:05                 ` Christian König
2022-01-13 13:05                   ` Christian König
2022-01-13 13:05                   ` Christian König
2022-01-13 13:05                   ` Christian König
2022-01-13 23:26                   ` John Stultz
2022-01-13 23:26                     ` John Stultz
2022-01-13 23:26                     ` John Stultz
2022-01-13 23:26                     ` John Stultz
2022-01-14  7:16                     ` Christian König
2022-01-14  7:16                       ` Christian König
2022-01-14  7:16                       ` Christian König
2022-01-14  7:16                       ` Christian König
2022-01-14 12:05                       ` Guangming.Cao
2022-01-14 12:05                         ` Guangming.Cao
2022-01-14 12:05                         ` Guangming.Cao
2022-01-15  1:17                         ` John Stultz
2022-01-15  1:17                           ` John Stultz
2022-01-15  1:17                           ` John Stultz
2022-01-15  1:17                           ` John Stultz
2022-01-19  9:59                           ` Guangming.Cao
2022-01-19  9:59                             ` Guangming.Cao
2022-01-19  9:59                             ` Guangming.Cao
2022-01-19 20:37                             ` John Stultz
2022-01-19 20:37                               ` John Stultz
2022-01-19 20:37                               ` John Stultz
2022-01-19 20:37                               ` John Stultz
2022-01-20  3:34                               ` [PATCH v4] dma-buf: system_heap: " guangming.cao
2022-01-20  3:34                                 ` guangming.cao
2022-01-20  3:34                                 ` guangming.cao
2022-01-20  3:34                                 ` guangming.cao
2022-01-20  3:48                                 ` John Stultz
2022-01-20  3:48                                   ` John Stultz
2022-01-20  3:48                                   ` John Stultz
2022-01-20  3:48                                   ` John Stultz
2022-01-20  7:08                                   ` [PATCH v5] " guangming.cao
2022-01-20  7:08                                     ` guangming.cao
2022-01-20  7:08                                     ` guangming.cao
2022-01-20  7:08                                     ` guangming.cao
2022-01-20  8:27                                     ` Christian König
2022-01-20  8:27                                       ` Christian König
2022-01-20  8:27                                       ` Christian König
2022-01-20  8:27                                       ` Christian König
2022-01-20  8:52                                       ` [PATCH v6] " guangming.cao
2022-01-20  8:52                                         ` guangming.cao
2022-01-20  8:52                                         ` guangming.cao
2022-01-20  8:52                                         ` guangming.cao
2022-01-20 10:00                                         ` [PATCH v6 RESEND] " guangming.cao
2022-01-20 10:00                                           ` guangming.cao
2022-01-20 10:00                                           ` guangming.cao
2022-01-20 10:00                                           ` guangming.cao
2022-01-20 10:22                                           ` Christian König [this message]
2022-01-20 10:22                                             ` Christian König
2022-01-20 10:22                                             ` Christian König
2022-01-20 10:22                                             ` Christian König

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=90bf495d-dbf6-cb0d-f54f-e0080b810f8d@amd.com \
    --to=christian.koenig@amd.com \
    --cc=benjamin.gaignard@linaro.org \
    --cc=bo.song@mediatek.com \
    --cc=caoguangming34@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=guangming.cao@mediatek.com \
    --cc=jianjiao.zeng@mediatek.com \
    --cc=john.stultz@linaro.org \
    --cc=labbott@redhat.com \
    --cc=libo.kang@mediatek.com \
    --cc=linaro-mm-sig@lists.linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=lmark@codeaurora.org \
    --cc=matthias.bgg@gmail.com \
    --cc=michael.j.ruhl@intel.com \
    --cc=mingyuan.ma@mediatek.com \
    --cc=sumit.semwal@linaro.org \
    --cc=wsd_upstream@mediatek.com \
    --cc=yf.wang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.