linux-kernel - Re: [GIT PULL] Power management and ACPI fixes for v3.10-rc5

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

Message-ID: <CA+8MBbJC9hKCjcZVK1tvpjr9DAwY_wAPmarqCWa7X-cq7Bph0A@mail.gmail.com>
Date:	Fri, 7 Jun 2013 16:02:11 -0700
From:	Tony Luck <tony.luck@...il.com>
To:	"Rafael J. Wysocki" <rjw@...k.pl>, Aaron Lu <aaron.lu@...el.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Linux PM list <linux-pm@...r.kernel.org>,
	ACPI Devel Maling List <linux-acpi@...r.kernel.org>
Subject: Re: [GIT PULL] Power management and ACPI fixes for v3.10-rc5

On Fri, Jun 7, 2013 at 3:23 PM, Tony Luck <tony.luck@...il.com> wrote:
> So please don't pull.

Bother. I see I was a few hours late finding this, and commit 9f29ab11ddb
is already in Linus' tree.

That's what happens when I get busy and skip a couple of days testing
linux-next :-(

So my problem comes from
arch/ia64/hp/common/sba_iommu.c

where the code in sba_init() says:

        acpi_bus_register_driver(&acpi_sba_ioc_driver);
        if (!ioc_list) {

but because of this change we never managed to call ioc_init()
so ioc_list doesn't get set up, and we die.
Before this commit, the call chain looked like this:

 [<a0000001011c3710>] ioc_init+0x40/0xd00
 [<a0000001011c4560>] acpi_sba_ioc_add+0x190/0x1c0
 [<a0000001005b3b40>] acpi_device_probe+0xa0/0x280
 [<a000000100850060>] really_probe+0xe0/0x520
 [<a0000001008504d0>] driver_probe_device+0x30/0x60
 [<a000000100850610>] __driver_attach+0x110/0x160
 [<a00000010084c550>] bus_for_each_dev+0x110/0x180
 [<a00000010084fcc0>] driver_attach+0x40/0x60
 [<a00000010084da90>] bus_add_driver+0x230/0x580
 [<a000000100851090>] driver_register+0xf0/0x400
 [<a0000001005b8670>] acpi_bus_register_driver+0x50/0x80
 [<a0000001011c45c0>] sba_init+0x30/0x2d0

Is my problem that this driver has (or attaches) a "scan handler"
where it shouldn't ... and I just need to stop it doing that?

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