linux-kernel - Re: [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-prev] [day] [month] [year] [list]

Date:	Fri, 14 Mar 2014 13:14:15 -0400
From:	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
To:	Stanislaw Gruszka <sgruszka@...hat.com>
Cc:	David Rientjes <rientjes@...gle.com>, boris.ostrovsky@...cle.com,
	david.vrabel@...rix.com, Ben Guthro <benjamin.guthro@...rix.com>,
	linux-kernel@...r.kernel.org,
	"Rafael J. Wysocki" <rjw@...ysocki.net>,
	xen-devel@...ts.xensource.com
Subject: Re: [BUG?] Interrupts enabled after
 xen_acpi_processor_resume+0x0/0x34 [xen_acpi_processor]

On Wed, Feb 26, 2014 at 11:26:21AM +0100, Stanislaw Gruszka wrote:
> On Mon, Feb 10, 2014 at 09:37:27AM -0500, Konrad Rzeszutek Wilk wrote:
> > > > But I'm not sure if that is good solution. It crate some not necessery
> > > > sysfs directories and files. Additionaly it can restore CPU C-states
> > > > after some other drivers resume, which prehaps require proper C-states.
> > > 
> > > Yes.
> > > > 
> > > > Hence maybe adding direct notify from xen core resume will be better
> > > > idea (proposed patch below). Plese let me know what you think, I'll
> > > > provide solution which you choose to bug reporters for testing.
> > > 
> > > Let me think about it for a day or so.
> > 
> > Sorry for the delay. I think this is fine.
> 
> I'm sorry for delay too. I provided test kernel with the patch to bug
> reporter, but have not get any answer since two weeks now.

I tested it and it works great.
> 
> I'll post the patch in the next email, I hope someone can test it (I'm
> not xen user). I'm pretty sure it fixes the problem, but not sure if it
> does not cause some crash. To test is enough to perform suspend/resume
> cycle (thought I'm not sure if suspended should be just guest or whole
> system with hypervisor).

I put your put in the queue for 3.15.

Thanks!
> 
> Thanks
> 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/