From: Dave Jiang <dave.jiang@intel.com>
To: Pan Bian <bianpan2016@163.com>,
"Williams, Dan J" <dan.j.williams@intel.com>,
"Koul, Vinod" <vinod.koul@intel.com>,
Julia Lawall <Julia.Lawall@lip6.fr>
Cc: "dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] dma: ioat: set error code on failures
Date: Thu, 1 Dec 2016 09:46:16 -0700 [thread overview]
Message-ID: <c7686f9e-bd4e-1de5-ce72-576da8e1dd0c@intel.com> (raw)
In-Reply-To: <1480576212-26518-1-git-send-email-bianpan2016@163.com>
On 12/01/2016 12:10 AM, Pan Bian wrote:
> Fix bug https://bugzilla.kernel.org/show_bug.cgi?id=188591. In function
> ioat_dma_self_test(), when the calls to dma_mapping_error() fails, the
> value of return variable err is 0 (indicates no error). As a result, the
> return value may be inconsistent with the execution status. This patch
> fixes the bug by assigning -ENOMEM to err on the error path.
>
> Signed-off-by: Pan Bian <bianpan2016@163.com>
Acked-by: Dave Jiang <dave.jiang@intel.com>
> ---
> drivers/dma/ioat/init.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/dma/ioat/init.c b/drivers/dma/ioat/init.c
> index 015f711..32383ef 100644
> --- a/drivers/dma/ioat/init.c
> +++ b/drivers/dma/ioat/init.c
> @@ -340,11 +340,13 @@ static int ioat_dma_self_test(struct ioatdma_device *ioat_dma)
> dma_src = dma_map_single(dev, src, IOAT_TEST_SIZE, DMA_TO_DEVICE);
> if (dma_mapping_error(dev, dma_src)) {
> dev_err(dev, "mapping src buffer failed\n");
> + err = -ENOMEM;
> goto free_resources;
> }
> dma_dest = dma_map_single(dev, dest, IOAT_TEST_SIZE, DMA_FROM_DEVICE);
> if (dma_mapping_error(dev, dma_dest)) {
> dev_err(dev, "mapping dest buffer failed\n");
> + err = -ENOMEM;
> goto unmap_src;
> }
> flags = DMA_PREP_INTERRUPT;
>
next prev parent reply other threads:[~2016-12-01 16:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-01 7:10 Pan Bian
2016-12-01 16:46 ` Dave Jiang [this message]
2016-12-02 10:32 ` Vinod Koul
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=c7686f9e-bd4e-1de5-ce72-576da8e1dd0c@intel.com \
--to=dave.jiang@intel.com \
--cc=Julia.Lawall@lip6.fr \
--cc=bianpan2016@163.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vinod.koul@intel.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
Powered by JetHome