From: Vinod Koul <vkoul@kernel.org>
To: Alexander.Barabash@dell.com
Cc: dmaengine@vger.kernel.org, alexander.barabash@gmail.com
Subject: Re: [PATCH v2] ioat: ioat_alloc_ring() failure handling.
Date: Fri, 27 Dec 2019 12:06:50 +0530 [thread overview]
Message-ID: <20191227063650.GH3006@vkoul-mobl> (raw)
In-Reply-To: <75e9c0e84c3345d693c606c64f8b9ab5@x13pwhopdag1307.AMER.DELL.COM>
On 25-12-19, 17:55, Alexander.Barabash@dell.com wrote:
> If dma_alloc_coherent() returns NULL in ioat_alloc_ring(), ring
> allocation must not proceed.
>
> Until now, if the first call to dma_alloc_coherent() in
> ioat_alloc_ring() returned NULL, the processing could proceed, failing
> with NULL-pointer dereferencing further down the line.
Applied, thanks
--
~Vinod
prev parent reply other threads:[~2019-12-27 6:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-25 17:55 [PATCH v2] ioat: ioat_alloc_ring() failure handling Alexander.Barabash
2019-12-26 15:48 ` Jiang, Dave
2019-12-27 6:36 ` Vinod Koul [this message]
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=20191227063650.GH3006@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=Alexander.Barabash@dell.com \
--cc=alexander.barabash@gmail.com \
--cc=dmaengine@vger.kernel.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