linux-kernel - [BUG?] Interrupts enabled after xen_acpi_processor_resume+0x0/0x34 [xen_acpi

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-next>] [day] [month] [year] [list]

Date:	Tue, 28 Jan 2014 16:08:49 +0100
From:	Stanislaw Gruszka <sgruszka@...hat.com>
To:	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
Cc:	Ben Guthro <benjamin.guthro@...rix.com>,
	linux-kernel@...r.kernel.org, "Rafael J. Wysocki" <rjw@...k.pl>
Subject: [BUG?] Interrupts enabled after xen_acpi_processor_resume+0x0/0x34
 [xen_acpi_processor]

Hi,

We have this bug report on our bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=1058268

In short:
WARNING: CPU: 0 PID: 6733 at drivers/base/syscore.c:104 syscore_resume+0x9a/0xe0()
Interrupts enabled after xen_acpi_processor_resume+0x0/0x34 [xen_acpi_processor]

Perhaps I'm wrong, but I think sysops->resume() callback should be
atomic i.e. can not use mutexes or kmalloc(,GFP_KERNEL), what is not
true regarding xen_acpi_processor_resume(). That callback was introduced
by commit 3fac10145b766a2244422788f62dc35978613fd8. Fixing that will
not be easy IMHO, but maybe you have some ideas ? :-)

Stanislaw
--
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/