[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130306155039.GB7697@redhat.com>
Date: Wed, 6 Mar 2013 16:50:39 +0100
From: Oleg Nesterov <oleg@...hat.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Mandeep Singh Baines <msb@...omium.org>,
linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org,
ibm-acpi@....eng.br, ibm-acpi-devel@...ts.sourceforge.net,
platform-driver-x86@...r.kernel.org, Aaron Lu <aaron.lu@...el.com>,
Henrique de Moraes Holschuh <hmh@....eng.br>,
Tejun Heo <tj@...nel.org>,
Maciej Rutecki <maciej.rutecki@...il.com>,
Artem Savkov <artem.savkov@...il.com>
Subject: Re: [PATCH] thinkpad-acpi: fix potential suspend blocking issue
On 03/05, Andrew Morton wrote:
>
> Basically the same as
> http://ozlabs.org/~akpm/mmots/broken-out/drivers-platform-x86-thinkpad_acpic-move-hotkey_thread_mutex-lock-after-set_freezable.patch.
> I think Artem's patch is a little better. There doesn't appear to be
> any locking protocol for tpacpi_lifecycle.
Which seems to have the same problem, hotkey_kthread() still calls
kthread_freezable_should_stop() under hotkey_thread_mutex.
IOW, we have two try_to_freeze's here, the patch moves only one of
them outside of the hotkey_thread_mutex.
Oleg.
--
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