From: Robin Murphy <robin.murphy@arm.com>
To: Tomasz Figa <tfiga@chromium.org>, iommu@lists.linux-foundation.org
Cc: linux-kernel@vger.kernel.org, Joerg Roedel <joro@8bytes.org>
Subject: Re: [PATCH 2/2] iommu/dma: use __GFP_NOWARN only for high-order allocations
Date: Tue, 27 Jun 2017 12:05:22 +0100 [thread overview]
Message-ID: <00da8d2c-d2e6-6462-d311-80ca4f515d24@arm.com> (raw)
In-Reply-To: <20170627072812.15316-2-tfiga@chromium.org>
On 27/06/17 08:28, Tomasz Figa wrote:
> Memory allocation routines are expected to report allocation errors to
> kernel log. However, current implementation of __iommu_dma_alloc_pages()
> adds __GFP_NOWARN for all calls to alloc_pages(), which completely
> disables any logging.
>
> Fix it by adding __GFP_NOWARN only to high order allocation attempts,
> which are not critical.
Makes sense to me.
Reviewed-by: Robin Murphy <robin.murphy@arm.com>
> Signed-off-by: Tomasz Figa <tfiga@chromium.org>
> ---
> drivers/iommu/dma-iommu.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/iommu/dma-iommu.c b/drivers/iommu/dma-iommu.c
> index 29965a092a69..8507987eed90 100644
> --- a/drivers/iommu/dma-iommu.c
> +++ b/drivers/iommu/dma-iommu.c
> @@ -433,6 +433,7 @@ static struct page **__iommu_dma_alloc_pages(unsigned int count,
> {
> struct page **pages;
> unsigned int i = 0, array_size = count * sizeof(*pages);
> + const gfp_t high_order_gfp = __GFP_NOWARN | __GFP_NORETRY;
>
> order_mask &= (2U << MAX_ORDER) - 1;
> if (!order_mask)
> @@ -452,8 +453,6 @@ static struct page **__iommu_dma_alloc_pages(unsigned int count,
> if (!(gfp & (__GFP_DMA | __GFP_DMA32)))
> gfp |= __GFP_HIGHMEM;
>
> - gfp |= __GFP_NOWARN;
> -
> while (count) {
> struct page *page = NULL;
> unsigned int order_size;
> @@ -469,7 +468,7 @@ static struct page **__iommu_dma_alloc_pages(unsigned int count,
>
> order_size = 1U << order;
> page = alloc_pages((order_mask - order_size) ?
> - gfp | __GFP_NORETRY : gfp, order);
> + gfp | high_order_gfp : gfp, order);
> if (!page)
> continue;
> if (!order)
>
next prev parent reply other threads:[~2017-06-27 11:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-27 7:28 [PATCH 1/2] iommu/dma: Respect __GFP_DMA and __GFP_DMA32 in incoming GFP flags Tomasz Figa
2017-06-27 7:28 ` [PATCH 2/2] iommu/dma: use __GFP_NOWARN only for high-order allocations Tomasz Figa
2017-06-27 11:05 ` Robin Murphy [this message]
2017-06-27 11:01 ` [PATCH 1/2] iommu/dma: Respect __GFP_DMA and __GFP_DMA32 in incoming GFP flags Robin Murphy
2017-06-27 11:17 ` Tomasz Figa
2017-06-27 12:26 ` Robin Murphy
2017-06-27 12:44 ` Tomasz Figa
2017-06-27 14:52 ` Robin Murphy
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=00da8d2c-d2e6-6462-d311-80ca4f515d24@arm.com \
--to=robin.murphy@arm.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tfiga@chromium.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®