From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Dan Carpenter <dan.carpenter@oracle.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] device property: fix a potential oops
Date: Wed, 04 May 2016 23:11:21 +0200 [thread overview]
Message-ID: <4978226.jACc6Brefu@vostro.rjw.lan> (raw)
In-Reply-To: <1461755060-138091-1-git-send-email-heikki.krogerus@linux.intel.com>
On Wednesday, April 27, 2016 02:04:20 PM Heikki Krogerus wrote:
> Since fwnode may hold ERR_PTR(-ENODEV) or it may point to
> NULL, the fwnode type checks is_of_node(), is_acpi_node()
> and is is_pset_node() need to consider it. Using
> IS_ERR_OR_NULL() to check it.
>
> Fixes: 0d67e0fa1664 ("device property: fix for a case of use-after-free")
> Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
> Signed-off-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Applied, thanks!
prev parent reply other threads:[~2016-05-04 21:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 11:04 [PATCH] device property: fix a potential oops Heikki Krogerus
2016-05-04 21:11 ` Rafael J. Wysocki [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=4978226.jACc6Brefu@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=dan.carpenter@oracle.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@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