From: Chris Diamand <chris.diamand@arm.com>
To: linux-pm@vger.kernel.org, MyungJoo Ham <myungjoo.ham@samsung.com>
Cc: Kyungmin Park <kyungmin.park@samsung.com>,
Nishanth Menon <nm@ti.com>, Cai Zhiyong <caizhiyong@huawei.com>
Subject: [PATCH] PM / devfreq: Don't delete sysfs group twice
Date: Tue, 13 Dec 2016 17:09:36 +0000 [thread overview]
Message-ID: <20161213170935.GA4661@e107465-lin.cambridge.arm.com> (raw)
The 'userspace' governor adds a sysfs entry, which is removed when
the governor is changed, or the devfreq device is released. However,
when the latter occurs via device_unregister(), device_del() is
called first, which removes the sysfs entries recursively and deletes
the kobject.
This means we get an Oops when the governor calls
sysfs_remove_group() on the deleted kobject. Fix this by explicitly
stopping the governor in devfreq_remove_device(), *before* the
devfreq entry is removed.
Note that we can't just remove the call to sysfs_remove_group() in
the userspace governor, as it's needed for when the governor is
changed to one without a sysfs entry.
Signed-off-by: Chris Diamand <chris.diamand@arm.com>
---
drivers/devfreq/devfreq.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/drivers/devfreq/devfreq.c b/drivers/devfreq/devfreq.c
index 478006b..d8a817c 100644
--- a/drivers/devfreq/devfreq.c
+++ b/drivers/devfreq/devfreq.c
@@ -622,6 +622,12 @@ int devfreq_remove_device(struct devfreq *devfreq)
if (!devfreq)
return -EINVAL;
+ if (devfreq->governor) {
+ devfreq->governor->event_handler(devfreq,
+ DEVFREQ_GOV_STOP, NULL);
+ devfreq->governor = NULL;
+ }
+
device_unregister(&devfreq->dev);
return 0;
--
1.9.1
next reply other threads:[~2016-12-13 17:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20161213171211epcas3p3ed8807883967daca28b7abe211446739@epcas3p3.samsung.com>
2016-12-13 17:09 ` Chris Diamand [this message]
2016-12-14 1:37 ` [PATCH] PM / devfreq: Don't delete sysfs group twice Chanwoo Choi
2016-12-14 1:38 ` Chanwoo Choi
2016-12-14 2:48 ` Chanwoo Choi
2016-12-14 9:29 ` Sudeep Holla
2016-12-14 10:10 ` Chanwoo Choi
[not found] ` <172e4f85358b4f4e9206c4a54b5db056@AM4PR0802MB2210.eurprd08.prod.outlook.com>
2016-12-14 11:32 ` Chris Diamand
2016-12-14 13:48 ` Chanwoo Choi
[not found] ` <7a342ead78be4f32a4a37b541fde412b@AM4PR0802MB2210.eurprd08.prod.outlook.com>
2016-12-15 10:41 ` Chris Diamand
2016-12-16 6:48 ` Chanwoo Choi
[not found] ` <f4620f8efbf247119640470ec12810fe@AM4PR0802MB2210.eurprd08.prod.outlook.com>
2016-12-16 19:09 ` [PATCH v2] " Chris Diamand
2016-12-16 2:17 ` Re: [PATCH] " MyungJoo Ham
[not found] <CGME20161213170941epcas2p1267d3da4c7034777c8de117ed3c0f9fe@epcas2p1.samsung.com>
2016-12-14 0:45 ` MyungJoo Ham
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=20161213170935.GA4661@e107465-lin.cambridge.arm.com \
--to=chris.diamand@arm.com \
--cc=caizhiyong@huawei.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-pm@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=nm@ti.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;
as well as URLs for NNTP newsgroup(s).