From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
John Youn <John.Youn@synopsys.com>,
linux-acpi@vger.kernel.org
Subject: [RESEND PATCH 0/2] device property: fix for two bugs
Date: Tue, 8 Mar 2016 15:44:35 +0200 [thread overview]
Message-ID: <1457444677-25645-1-git-send-email-heikki.krogerus@linux.intel.com> (raw)
Hi Rafael,
I'm resending these for your convenience.
> The fwnode->secondary is causing problems when a property_set is
> providing the primary fwnode.
>
> Both of these fixes are a bit clumsy looking IMO, but I didn't have
> better ideas. I think the second one fixing the use-after-free bug
> should ideally be taken care of in set_secondary_fwnode() instead of
> device_remove_property_set(), but I didn't have any ideas how to do
> that.
There were no better ideas that would have worked from anybody, so
I'm proposing we go forward with these for now.
Heikki Krogerus (2):
device property: fwnode->secondary may contain ERR_PTR(-ENODEV)
device property: fix for a case of use-after-free
drivers/base/property.c | 13 +++++++------
1 file changed, 7 insertions(+), 6 deletions(-)
--
2.7.0
next reply other threads:[~2016-03-08 13:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 13:44 Heikki Krogerus [this message]
2016-03-08 13:44 ` [RESEND PATCH 1/2] device property: fwnode->secondary may contain ERR_PTR(-ENODEV) Heikki Krogerus
2016-03-09 0:31 ` Rafael J. Wysocki
2016-03-08 13:44 ` [RESEND PATCH 2/2] device property: fix for a case of use-after-free Heikki Krogerus
2016-03-09 0:52 ` Rafael J. Wysocki
2016-03-09 14:41 ` Heikki Krogerus
2016-03-10 8:44 ` Heikki Krogerus
2016-03-10 9:17 ` Heikki Krogerus
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=1457444677-25645-1-git-send-email-heikki.krogerus@linux.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=John.Youn@synopsys.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rjw@rjwysocki.net \
/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).