linux-kernel - Re: [REGRESSION] b8b2c7d845 breaks suspend/resume in qemu

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CALAqxLWjBP=iyAb=Rm3Z5Y3RNPwFy-KGmag0a5KGu97VYRO+aQ@mail.gmail.com>
Date:	Wed, 2 Dec 2015 13:31:38 -0800
From:	John Stultz <john.stultz@...aro.org>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:	martin.wilck@...fujitsu.com,
	Uwe Kleine-König 
	<u.kleine-koenig@...gutronix.de>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: [REGRESSION] b8b2c7d845 breaks suspend/resume in qemu

On Wed, Dec 2, 2015 at 12:57 PM, Greg Kroah-Hartman
<gregkh@...uxfoundation.org> wrote:
> On Wed, Dec 02, 2015 at 12:46:10PM -0800, John Stultz wrote:
>> On Wed, Dec 2, 2015 at 12:39 PM, John Stultz <john.stultz@...aro.org> wrote:
>> > Hey Uwe,
>> >
>> > So I recently noticed that my alarmtimer suspend/resume tests
>> > (selftests/timers/alartimer-suspend.c) were getting stuck testing w/
>> > 4.4-rc kernels when running under qemu (x86_64).
>> >
>> > I've bisected this back to: b8b2c7d845 (base/platform: assert that
>> > dev_pm_domain callbacks are called unconditionally).
>> >
>> > I've not yet spent done any further analysis (bisecting it down, after
>> > some user-error, ate up my morning). But I wanted to see if there were
>> > any initial suggestions for solving this.
>>
>> Just one other quick note: Reverting this commit against 4.4-rc3 seems
>> to work as well.
>
> There's a proposed patch to resolve this on the mailing list, "Subject:
> [PATCH] base/platform: fix panic when probe function is NULL" from
> Martin, but I think he's going to send me an updated version before I
> forward it on to Linus.
>
> It should resolve your issue, can you verify that?

Yep. That fix seems to avoid the problem for me.

thanks
-john
--
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/