linux-kernel - Re: Meet the bugs for linux-3.19-rc4 on aarch64 board

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: <20150204170951.GE26006@e104818-lin.cambridge.arm.com>
Date:	Wed, 4 Feb 2015 17:09:51 +0000
From:	Catalin Marinas <catalin.marinas@....com>
To:	Ding Tianhong <dingtianhong@...wei.com>
Cc:	Will Deacon <Will.Deacon@....com>, Arnd Bergmann <arnd@...db.de>,
	Linuxarm <linuxarm@...wei.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: Meet the bugs for linux-3.19-rc4 on aarch64 board

On Wed, Feb 04, 2015 at 03:17:25PM +0000, Ding Tianhong wrote:
> bad mode in Synchronous Abort handler detected, code 0x86000005
> CPU: 1 PID: 381 Comm: kworker/1:1 Tainted: G           O   3.19.0-rc4+ #6
> Hardware name: Hisilicon Board ESL (DT)
> Workqueue: events           (null)
> task: ffffffc01cdb5800 ti: ffffffc01db28000 task.ti: ffffffc01db28000
> PC is at 0x0
> LR is at process_one_work+0x144/0x33c

This looks like process_one_work() tried to execute address 0, possibly
when it does:

	worker->current_func(work);

> Internal error: Oops - bad mode: 0 [#1] SMP
> Modules linked in: sre(O)
> CPU: 1 PID: 381 Comm: kworker/1:1 Tainted: G           O   3.19.0-rc4+ #6
> Hardware name: Hisilicon Board ESL (DT)
> Workqueue: events           (null)

So there is an "events" workqueue with a NULL function which
process_one_work() tries to call. You could add some more debugging in
this function or you could start bisecting (could check 3.18 first).

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