From: Mark Brown <broonie@kernel.org>
To: Pankaj Dubey <pankaj.dubey@samsung.com>
Cc: linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org,
Li.Xiubo@freescale.com, naushad@samsung.com
Subject: Re: [PATCH] regmap: fix NULL pointer dereference in _regmap_write/read
Date: Sat, 27 Sep 2014 12:20:19 +0100 [thread overview]
Message-ID: <20140927112019.GJ27755@sirena.org.uk> (raw)
In-Reply-To: <1411791475-27031-1-git-send-email-pankaj.dubey@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 328 bytes --]
On Sat, Sep 27, 2014 at 09:47:55AM +0530, Pankaj Dubey wrote:
> If LOG_DEVICE is defined and map->dev is NULL it will lead to NULL
> pointer dereference. This patch fixes this issue by adding check for
> dev->NULL in all such places in regmap.c
This doesn't apply against current code since the same fix has already
been made.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2014-09-27 11:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-27 4:17 [PATCH] regmap: fix NULL pointer dereference in _regmap_write/read Pankaj Dubey
2014-09-27 11:20 ` Mark Brown [this message]
2014-09-27 11:21 ` Mark Brown
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=20140927112019.GJ27755@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Li.Xiubo@freescale.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=naushad@samsung.com \
--cc=pankaj.dubey@samsung.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 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.