All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
To: jean-philippe.brucker-5wv7dgnIgG8@public.gmane.org
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
	Robin Murphy <robin.murphy-5wv7dgnIgG8@public.gmane.org>
Subject: [bug report] iommu/io-pgtable-arm: Fix pgtable allocation in selftest
Date: Wed, 10 Apr 2019 12:34:06 +0300	[thread overview]
Message-ID: <20190410093405.GA9889@kadam> (raw)

Hello Jean-Philippe Brucker,

This is a semi-automatic email about new static checker warnings.

The patch fac83d29d954: "iommu/io-pgtable-arm: Fix pgtable allocation
in selftest" from Jun 18, 2018, leads to the following Smatch
complaint:

    drivers/iommu/io-pgtable-arm.c:246 __arm_lpae_alloc_pages()
    error: we previously assumed 'dev' could be null (see line 239)

drivers/iommu/io-pgtable-arm.c
   238		VM_BUG_ON((gfp & __GFP_HIGHMEM));
   239		p = alloc_pages_node(dev ? dev_to_node(dev) : NUMA_NO_NODE,
                                     ^^^
We added a NULL check here

   240				     gfp | __GFP_ZERO, order);
   241		if (!p)
   242			return NULL;
   243	
   244		pages = page_address(p);
   245		if (!(cfg->quirks & IO_PGTABLE_QUIRK_NO_DMA)) {
   246			dma = dma_map_single(dev, pages, size, DMA_TO_DEVICE);
                                             ^^^
But dma_map_single() can't take a NULL argument either.

   247			if (dma_mapping_error(dev, dma))
   248				goto out_free;

I don't know why this warning is only showing up now, almost a year
later.  Sorry about that.

regards,
dan carpenter

WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: jean-philippe.brucker@arm.com
Cc: iommu@lists.linux-foundation.org, Robin Murphy <robin.murphy@arm.com>
Subject: [bug report] iommu/io-pgtable-arm: Fix pgtable allocation in selftest
Date: Wed, 10 Apr 2019 12:34:06 +0300	[thread overview]
Message-ID: <20190410093405.GA9889@kadam> (raw)
Message-ID: <20190410093406.W4mGocrccrCScxrCwR3b7c3psBgFLFZraLaBjriqKiM@z> (raw)

Hello Jean-Philippe Brucker,

This is a semi-automatic email about new static checker warnings.

The patch fac83d29d954: "iommu/io-pgtable-arm: Fix pgtable allocation
in selftest" from Jun 18, 2018, leads to the following Smatch
complaint:

    drivers/iommu/io-pgtable-arm.c:246 __arm_lpae_alloc_pages()
    error: we previously assumed 'dev' could be null (see line 239)

drivers/iommu/io-pgtable-arm.c
   238		VM_BUG_ON((gfp & __GFP_HIGHMEM));
   239		p = alloc_pages_node(dev ? dev_to_node(dev) : NUMA_NO_NODE,
                                     ^^^
We added a NULL check here

   240				     gfp | __GFP_ZERO, order);
   241		if (!p)
   242			return NULL;
   243	
   244		pages = page_address(p);
   245		if (!(cfg->quirks & IO_PGTABLE_QUIRK_NO_DMA)) {
   246			dma = dma_map_single(dev, pages, size, DMA_TO_DEVICE);
                                             ^^^
But dma_map_single() can't take a NULL argument either.

   247			if (dma_mapping_error(dev, dma))
   248				goto out_free;

I don't know why this warning is only showing up now, almost a year
later.  Sorry about that.

regards,
dan carpenter
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

             reply	other threads:[~2019-04-10  9:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-10  9:34 Dan Carpenter [this message]
2019-04-10  9:34 ` [bug report] iommu/io-pgtable-arm: Fix pgtable allocation in selftest Dan Carpenter
2019-04-10  9:44 ` Robin Murphy
2019-04-10  9:44   ` Robin Murphy
     [not found]   ` <782a999e-ce70-bd8e-5a7b-cd320ce98144-5wv7dgnIgG8@public.gmane.org>
2019-04-10 10:02     ` Dan Carpenter
2019-04-10 10:02       ` Dan Carpenter

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=20190410093405.GA9889@kadam \
    --to=dan.carpenter-qhclzuegtsvqt0dzr+alfa@public.gmane.org \
    --cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=jean-philippe.brucker-5wv7dgnIgG8@public.gmane.org \
    --cc=robin.murphy-5wv7dgnIgG8@public.gmane.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 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.