From: Ian Abbott <abbotti@mev.co.uk>
To: H Hartley Sweeten <hsweeten@visionengravers.com>,
devel@linuxdriverproject.org
Cc: gregkh@linuxfoundation.org, "# 4 . 0+" <stable@vger.kernel.org>
Subject: Re: [PATCH 1/3] staging: comedi: das1800: fix possible NULL dereference
Date: Mon, 11 Apr 2016 10:31:40 +0100 [thread overview]
Message-ID: <570B6EFC.2040802@mev.co.uk> (raw)
In-Reply-To: <1460135700-17749-2-git-send-email-hsweeten@visionengravers.com>
On 08/04/16 18:14, H Hartley Sweeten wrote:
> DMA is optional with this driver. If it was not enabled the devpriv->dma
> pointer will be NULL.
>
> Fix the possible NULL pointer dereference when trying to disable the DMA
> channels in das1800_ai_cancel() and tidy up the comments to fix the
> checkpatch.pl issues:
> WARNING: line over 80 characters
>
> It's probably harmless in das1800_ai_setup_dma() because the 'desc' pointer
> will not be used if DMA is disabled but fix it there also.
>
> Fixes: 99dfc3357e98 ("staging: comedi: das1800: remove depends on ISA_DMA_API limitation")
> Cc: <stable@vger.kernel.org> # 4.0+
> Signed-off-by: H Hartley Sweeten <hsweeten@visionengravers.com>
> Cc: Ian Abbott <abbotti@mev.co.uk>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> ---
> drivers/staging/comedi/drivers/das1800.c | 22 +++++++++++++---------
> 1 file changed, 13 insertions(+), 9 deletions(-)
>
Thanks!
Reviewed-by: Ian Abbott <abbotti@mev.co.uk>
(I've already reviewed the other two.)
--
-=( Ian Abbott @ MEV Ltd. E-mail: <abbotti@mev.co.uk> )=-
-=( Web: http://www.mev.co.uk/ )=-
prev parent reply other threads:[~2016-04-11 9:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1460135700-17749-1-git-send-email-hsweeten@visionengravers.com>
2016-04-08 17:14 ` [PATCH 1/3] staging: comedi: das1800: fix possible NULL dereference H Hartley Sweeten
2016-04-11 9:31 ` Ian Abbott [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=570B6EFC.2040802@mev.co.uk \
--to=abbotti@mev.co.uk \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=hsweeten@visionengravers.com \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).