linux-kernel - Re: [3.9-rc1 x86] Bug in ioremap code?

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 for Android: free password hash cracker in your pocket

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

Message-ID: <51376453.3030308@linux.vnet.ibm.com>
Date:	Wed, 06 Mar 2013 07:44:19 -0800
From:	Dave Hansen <dave@...ux.vnet.ibm.com>
To:	Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
CC:	bp@...en8.de, hpa@...ux.intel.com, linux-kernel@...r.kernel.org
Subject: Re: [3.9-rc1 x86] Bug in ioremap code?

On 03/06/2013 06:58 AM, Tetsuo Handa wrote:
> I don't know why but changing kernel config to CONFIG_ACPI=n
> ( http://I-love.SAKURA.ne.jp/tmp/config-3.9-rc1-noacpi ) solves this bug.
> Well, should I run bisection on ACPI code?

The ACPI code definitely _triggers_ it.  However, if you bisect, I bet
you'll just bisect down to the new debugging check that you're hitting:

http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a25b9316841c5afa226f8f70a457861b35276a92

So, if you're able to bisect it, you'll need to apply that patch
whenever you're at a bisect point _before_ it was applied.  That might
also mean doing some merging because I'm sure the code around there has
changed.  IOW, bisecting isn't going to be super-easy.

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