From: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>, Toshi Kani <toshi.kani@hp.com>
Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
LKML <linux-kernel@vger.kernel.org>,
Yinghai Lu <yinghai@kernel.org>, Jiang Liu <liuj97@gmail.com>
Subject: Re: [Update 3][PATCH 2/7] ACPI / scan: Introduce common code for ACPI-based device hotplug
Date: Fri, 22 Feb 2013 17:51:28 +0900 [thread overview]
Message-ID: <51273190.7030106@jp.fujitsu.com> (raw)
In-Reply-To: <11658900.TkhCHmg9LJ@vostro.rjw.lan>
[-- Attachment #1: Type: text/plain, Size: 5350 bytes --]
2013/02/22 10:50, Rafael J. Wysocki wrote:
> On Thursday, February 21, 2013 06:12:21 PM Toshi Kani wrote:
>> On Fri, 2013-02-22 at 00:06 +0100, Rafael J. Wysocki wrote:
>>> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>>>
>>> Multiple drivers handling hotplug-capable ACPI device nodes install
>>> notify handlers covering the same types of events in a very similar
>>> way. Moreover, those handlers are installed in separate namespace
>>> walks, although that really should be done during namespace scans
>>> carried out by acpi_bus_scan(). This leads to substantial code
>>> duplication, unnecessary overhead and behavior that is hard to
>>> follow.
>>>
>>> For this reason, introduce common code in drivers/acpi/scan.c for
>>> handling hotplug-related notification and carrying out device
>>> insertion and eject operations in a generic fashion, such that it
>>> may be used by all of the relevant drivers in the future. To cover
>>> the existing differences between those drivers introduce struct
>>> acpi_hotplug_profile for representing collections of hotplug
>>> settings associated with different ACPI scan handlers that can be
>>> used by the drivers to make the common code reflect their current
>>> behavior.
>>>
>>> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>>> ---
>>>
>>> This update fixes an issue pointed out by Toshi Kani (that
>>> ACPI_OST_EC_OSPM_* event source codes should not be used with _OST for events
>>> that we received a notification for from the platform firmware).
>>>
>>> Thanks,
>>> Rafael
>>>
>>> ---
>>> drivers/acpi/scan.c | 270 ++++++++++++++++++++++++++++++++++++++----------
>>> include/acpi/acpi_bus.h | 7 +
>>> 2 files changed, 224 insertions(+), 53 deletions(-)
>> :
>>> +static void acpi_bus_device_eject(void *context)
>>> +{
>>> + acpi_handle handle = context;
>>> + struct acpi_device *device = NULL;
>>> + struct acpi_scan_handler *handler;
>>> + u32 ost_code = ACPI_OST_SC_NON_SPECIFIC_FAILURE;
>>> +
>>> + mutex_lock(&acpi_scan_lock);
>>> +
>>> + acpi_bus_get_device(handle, &device);
>>> + if (!device)
>>> + goto err_out;
>>> +
>>> + handler = device->handler;
>>> + if (!handler || !handler->hotplug.enabled) {
>>> + ost_code = ACPI_OST_SC_EJECT_NOT_SUPPORTED;
>>> + goto err_out;
>>> + }
>>> + acpi_evaluate_hotplug_ost(handle, ACPI_NOTIFY_EJECT_REQUEST,
>>> + ACPI_OST_SC_EJECT_IN_PROGRESS, NULL);
>>> + if (handler->hotplug.autoeject) {
>>> + int error;
>>> +
>>> + get_device(&device->dev);
>>> + error = acpi_scan_hot_remove(device);
>>> + if (error)
>>> + goto err_out;
>>> + } else {
>>> + device->flags.eject_pending = true;
>>> }
>>> + if (handler->hotplug.uevents)
>>> + kobject_uevent(&device->dev.kobj, KOBJ_OFFLINE);
>>
>> I confirmed that the _OST issue with hot-add is fixed. Here is a new
>> one. When autoeject is enabled, it crashes in kobject_uevent() since
>> the device is no longer valid.
>
> Well, this one is more difficult.
>
> I can change the ordering so that kobject_uevent() is called before
> acpi_scan_hot_remove(), but then user space may not know that the device is
> being removed at the moment (which still may fail). Still, maybe this is
> OK, because user space will get KOBJ_REMOVE when the device actually goes
> away anyway.
>
> Or perhaps we can emit KOBJ_OFFLINE before acpi_scan_hot_remove() and if
> it fails, emit KOBJ_ONLINE?
How about following patch? My system cannot send EJECT notification.
So I have not tested this patch.
# Recently when I send a patch, tabs of the patch is changed to spaces often.
# So I attached the patch.
---
When hotplug.autoeject and uevents are enabled, it crashes in
kobject_uevent() since the device is no longer valid.
This patch fixes the problem.
Reported-by: Toshi Kani <toshi.kani@hp.com>
Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
---
drivers/acpi/scan.c | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
Index: linux-pm/drivers/acpi/scan.c
===================================================================
--- linux-pm.orig/drivers/acpi/scan.c 2013-02-22 16:02:07.000000000 +0900
+++ linux-pm/drivers/acpi/scan.c 2013-02-22 16:06:36.792816699 +0900
@@ -139,9 +139,6 @@ static int acpi_scan_hot_remove(struct a
"Hot-removing device %s...\n", dev_name(&device->dev)));
acpi_bus_trim(device);
- /* Device node has been unregistered. */
- put_device(&device->dev);
- device = NULL;
if (ACPI_SUCCESS(acpi_get_handle(handle, "_LCK", ¬_used))) {
arg_list.count = 1;
@@ -191,10 +188,10 @@ static void acpi_bus_device_eject(void *
}
acpi_evaluate_hotplug_ost(handle, ACPI_NOTIFY_EJECT_REQUEST,
ACPI_OST_SC_EJECT_IN_PROGRESS, NULL);
+ get_device(&device->dev);
if (handler->hotplug.autoeject) {
int error;
- get_device(&device->dev);
error = acpi_scan_hot_remove(device);
if (error)
goto err_out;
@@ -204,6 +201,7 @@ static void acpi_bus_device_eject(void *
if (handler->hotplug.uevents)
kobject_uevent(&device->dev.kobj, KOBJ_OFFLINE);
+ put_device(&device->dev);
out:
mutex_unlock(&acpi_scan_lock);
return;
@@ -312,6 +310,7 @@ void acpi_bus_hot_remove_device(void *co
ACPI_OST_SC_NON_SPECIFIC_FAILURE,
NULL);
+ put_device(&acpi_device->dev);
mutex_unlock(&acpi_scan_lock);
kfree(context);
}
[-- Attachment #2: fix-panic-in-kobject_uevent.patch --]
[-- Type: text/x-patch, Size: 1712 bytes --]
When hotplug.autoeject and uevents are enabled, it crashes in
kobject_uevent() since the device is no longer valid.
This patch fixes the problem.
Reported-by: Toshi Kani <toshi.kani@hp.com>
Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
---
drivers/acpi/scan.c | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
Index: linux-pm/drivers/acpi/scan.c
===================================================================
--- linux-pm.orig/drivers/acpi/scan.c 2013-02-22 16:02:07.000000000 +0900
+++ linux-pm/drivers/acpi/scan.c 2013-02-22 16:06:36.792816699 +0900
@@ -139,9 +139,6 @@ static int acpi_scan_hot_remove(struct a
"Hot-removing device %s...\n", dev_name(&device->dev)));
acpi_bus_trim(device);
- /* Device node has been unregistered. */
- put_device(&device->dev);
- device = NULL;
if (ACPI_SUCCESS(acpi_get_handle(handle, "_LCK", ¬_used))) {
arg_list.count = 1;
@@ -191,10 +188,10 @@ static void acpi_bus_device_eject(void *
}
acpi_evaluate_hotplug_ost(handle, ACPI_NOTIFY_EJECT_REQUEST,
ACPI_OST_SC_EJECT_IN_PROGRESS, NULL);
+ get_device(&device->dev);
if (handler->hotplug.autoeject) {
int error;
- get_device(&device->dev);
error = acpi_scan_hot_remove(device);
if (error)
goto err_out;
@@ -204,6 +201,7 @@ static void acpi_bus_device_eject(void *
if (handler->hotplug.uevents)
kobject_uevent(&device->dev.kobj, KOBJ_OFFLINE);
+ put_device(&device->dev);
out:
mutex_unlock(&acpi_scan_lock);
return;
@@ -312,6 +310,7 @@ void acpi_bus_hot_remove_device(void *co
ACPI_OST_SC_NON_SPECIFIC_FAILURE,
NULL);
+ put_device(&acpi_device->dev);
mutex_unlock(&acpi_scan_lock);
kfree(context);
}
next prev parent reply other threads:[~2013-02-22 8:53 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-17 15:18 [PATCH 0/7] ACPI / hotplug: Common code for ACPI-based hotplug Rafael J. Wysocki
2013-02-17 15:20 ` [PATCH 1/7] ACPI / scan: Introduce acpi_scan_match_handler() Rafael J. Wysocki
2013-02-19 6:48 ` Yasuaki Ishimatsu
2013-02-17 15:21 ` [PATCH 2/7] ACPI / scan: Introduce common code for ACPI-based device hotplug Rafael J. Wysocki
2013-02-19 6:43 ` Yasuaki Ishimatsu
2013-02-19 7:10 ` Yasuaki Ishimatsu
2013-02-20 13:27 ` Rafael J. Wysocki
2013-02-20 13:23 ` Rafael J. Wysocki
2013-02-20 20:23 ` Toshi Kani
2013-02-20 21:17 ` Rafael J. Wysocki
2013-02-20 22:49 ` [Update][PATCH " Rafael J. Wysocki
2013-02-21 1:17 ` Toshi Kani
2013-02-21 15:44 ` Rafael J. Wysocki
2013-02-21 15:52 ` [Update 2][PATCH " Rafael J. Wysocki
2013-02-21 17:39 ` Toshi Kani
2013-02-21 22:57 ` Rafael J. Wysocki
2013-02-21 23:06 ` [Update 3][PATCH " Rafael J. Wysocki
2013-02-22 1:12 ` Toshi Kani
2013-02-22 1:50 ` Rafael J. Wysocki
2013-02-22 8:51 ` Yasuaki Ishimatsu [this message]
2013-02-22 12:37 ` Rafael J. Wysocki
2013-02-22 15:54 ` Toshi Kani
2013-02-22 20:59 ` Rafael J. Wysocki
2013-02-23 22:38 ` [Update 4][PATCH " Rafael J. Wysocki
2013-02-25 18:07 ` Toshi Kani
2013-02-25 23:39 ` Rafael J. Wysocki
2013-02-25 23:32 ` Toshi Kani
2013-02-26 0:40 ` Yasuaki Ishimatsu
2013-02-26 1:09 ` Toshi Kani
2013-02-26 2:02 ` Yasuaki Ishimatsu
2013-02-26 3:11 ` Rafael J. Wysocki
2013-02-26 3:40 ` Yasuaki Ishimatsu
2013-02-26 3:50 ` Rafael J. Wysocki
2013-03-04 13:10 ` Vasilis Liaskovitis
2013-03-14 17:16 ` Rafael J. Wysocki
2013-03-15 10:47 ` Vasilis Liaskovitis
2013-03-25 20:45 ` Toshi Kani
2013-03-25 22:29 ` Rafael J. Wysocki
2013-03-25 22:57 ` Toshi Kani
2013-03-26 12:22 ` Rafael J. Wysocki
2013-03-26 20:10 ` Toshi Kani
2013-02-17 15:22 ` [PATCH 3/7] ACPI / container: Use common hotplug code Rafael J. Wysocki
2013-02-17 15:23 ` [PATCH 4/7] ACPI / scan: Introduce acpi_scan_handler_matching() Rafael J. Wysocki
2013-02-19 8:05 ` Yasuaki Ishimatsu
2013-02-17 15:24 ` [PATCH 5/7] ACPI / hotplug: Introduce user space interface for hotplug profiles Rafael J. Wysocki
2013-02-25 18:13 ` Toshi Kani
2013-02-25 23:25 ` Rafael J. Wysocki
2013-02-17 15:25 ` [PATCH 6/7] ACPI / container: Use hotplug profile user space interface Rafael J. Wysocki
2013-02-17 15:27 ` [PATCH 7/7] ACPI / scan: Make memory hotplug driver use struct acpi_scan_handler Rafael J. Wysocki
2013-02-19 18:11 ` Vasilis Liaskovitis
2013-02-20 3:35 ` Yasuaki Ishimatsu
2013-02-20 10:42 ` Vasilis Liaskovitis
2013-02-20 21:50 ` Toshi Kani
2013-02-20 22:29 ` Rafael J. Wysocki
2013-02-20 22:39 ` Toshi Kani
2013-02-21 6:58 ` Yasuaki Ishimatsu
2013-02-26 22:41 ` [PATCH v2, 0/7] ACPI / hotplug: Common code for ACPI-based hotplug Rafael J. Wysocki
2013-02-26 22:44 ` [PATCH v2, 1/7] ACPI / scan: Introduce acpi_scan_match_handler() Rafael J. Wysocki
2013-02-26 22:46 ` [PATCH v2, 2/7] ACPI / scan: Introduce common code for ACPI-based device hotplug Rafael J. Wysocki
2013-02-26 22:46 ` [PATCH v2, 3/7] ACPI / container: Use common hotplug code Rafael J. Wysocki
2013-02-26 23:13 ` Toshi Kani
2013-02-27 0:06 ` Rafael J. Wysocki
2013-02-27 0:09 ` [Update][PATCH " Rafael J. Wysocki
2013-02-26 22:47 ` [PATCH v2, 4/7] ACPI / scan: Introduce acpi_scan_handler_matching() Rafael J. Wysocki
2013-02-26 22:48 ` [PATCH v2, 5/7] ACPI / hotplug: Introduce user space interface for hotplug profiles Rafael J. Wysocki
2013-02-26 22:49 ` [PATCH v2, 6/7] ACPI / container: Use hotplug profile user space interface Rafael J. Wysocki
2013-02-26 22:50 ` [PATCH v2, 7/7] ACPI / scan: Make memory hotplug driver use struct acpi_scan_handler Rafael J. Wysocki
2013-02-27 0:51 ` [PATCH v2, 0/7] ACPI / hotplug: Common code for ACPI-based hotplug Toshi Kani
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=51273190.7030106@jp.fujitsu.com \
--to=isimatu.yasuaki@jp.fujitsu.com \
--cc=bhelgaas@google.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuj97@gmail.com \
--cc=rjw@sisk.pl \
--cc=toshi.kani@hp.com \
--cc=yinghai@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