From: Wen Congyang <wency@cn.fujitsu.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
linux-acpi@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: acpi_memhotplug.c: don't allow to eject the memory device if it is being used
Date: Thu, 08 Nov 2012 18:03:15 +0800 [thread overview]
Message-ID: <509B8363.1090500@cn.fujitsu.com> (raw)
In-Reply-To: <1868139.0d5iSM0t2m@vostro.rjw.lan>
At 11/08/2012 05:58 PM, Rafael J. Wysocki Wrote:
> On Thursday, November 08, 2012 05:33:43 PM Wen Congyang wrote:
>> Hi, Rafael J. Wysocki
>>
>> At 11/06/2012 10:05 PM, Dan Carpenter Wrote:
>>> On Tue, Nov 06, 2012 at 10:10:11AM +0800, Wen Congyang wrote:
>>>> At 11/06/2012 02:11 AM, Dan Carpenter Wrote:
>>>>> Hello Wen Congyang,
>>>>>
>>>>> The patch 306859f13dc1: "acpi_memhotplug.c: don't allow to eject the
>>>>> memory device if it is being used" from Nov 3, 2012, leads to the
>>>>> following Smatch warning:
>>>>> drivers/acpi/acpi_memhotplug.c:367 acpi_memory_remove_memory()
>>>>> warn: inconsistent returns mutex:&mem_device->list_lock:
>>>>> locked (357,361) unlocked (367)
>>>>
>>>> Thanks for pointing it out.
>>>>
>>>> The patch 306859f13dc1 is in akpm's tree, and it conflicts with another
>>>> patch in linux-pm's tree. So Andrew Morton drops them.
>>>>
>>>> I will resend them based on linux-pm's next tree.
>>>
>>> Ok. Today's linux-next version 85fcb3758c10e "ACPI / memory-hotplug:
>>> introduce a mutex lock to protect the list in acpi_memory_device"
>>> has a similar problem and should be fixed as well.
>>
>> This patch is in pm tree, and there is one problem. Should I resend them?
>
> Yes, please.
>
> Please also let me know which commits in linux-pm.git/linux-next should be
> replaced with the new versions.
OK. I will write it in the patches.
Thanks
Wen Congyang
>
> Thanks,
> Rafael
>
>
prev parent reply other threads:[~2012-11-08 9:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-05 18:11 acpi_memhotplug.c: don't allow to eject the memory device if it is being used Dan Carpenter
2012-11-06 2:10 ` Wen Congyang
2012-11-06 14:05 ` Dan Carpenter
2012-11-07 1:39 ` Wen Congyang
2012-11-08 9:33 ` Wen Congyang
2012-11-08 9:58 ` Rafael J. Wysocki
2012-11-08 10:03 ` Wen Congyang [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=509B8363.1090500@cn.fujitsu.com \
--to=wency@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=dan.carpenter@oracle.com \
--cc=linux-acpi@vger.kernel.org \
--cc=rjw@sisk.pl \
/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).