| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Thu, 01 Nov 2012 09:40:27 +0800 From: Tang Chen <tangchen@...fujitsu.com> To: Yasuaki Ishimatsu <isimatu.yasuaki@...fujitsu.com>, yinghai@...nel.org CC: bhelgaas@...gle.com, lenb@...nel.org, jiang.liu@...wei.com, izumi.taku@...fujitsu.com, linux-acpi@...r.kernel.org, linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH v3 0/3] ACPI: container hot remove support. On 10/31/2012 07:09 PM, Yasuaki Ishimatsu wrote: > Hi Tang, > > If container device contains memory device, the function is > very danger. As you know, we are developing a memory hotplug. > If memory has kernel memory, memory hot remove operations fails. > But container_device_remove() cannot realize it. So even if > the memory hot remove operation fails, container_device_remove() > keeps hot remove operation. Finally, the function sends _EJ0 > to firmware. In this case, if the memory is accessed, kernel > panic occurs. > The example is as follows: > > https://lkml.org/lkml/2012/9/26/318 > Hi Ishimatsu, I see, thanks for the info. So we need to do some roll back thing. Is anyone doing this now ? If yes, would you please give me some links to refer to ? And I think I should push these patches later. If not, I think I can try to do it. Thanks. :) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists