linux-kernel - Re: BUG: spinlock lockup suspected on CPU#0, flush-ubifs_0

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:	Thu, 16 May 2013 12:54:20 +0300
From:	Artem Bityutskiy <dedekind1@...il.com>
To:	Mark Jackson <mpfj-list@...flow.co.uk>
Cc:	"linux-mtd@...ts.infradead.org" <linux-mtd@...ts.infradead.org>,
	adrian.hunter@...el.com, lkml <linux-kernel@...r.kernel.org>
Subject: Re: BUG: spinlock lockup suspected on CPU#0, flush-ubifs_0_0/844

On Fri, 2013-04-26 at 15:08 +0100, Mark Jackson wrote:
> I've encountered a lockup on ubifs ... any ideas ?
> 
> # ifup eth1
> [ 3451.254040] Unable to handle kernel NULL pointer dereference at virtual address 00000000
> [ 3451.262627] pgd = cf468000
> [ 3451.265489] [00000000] *pgd=8f48c831, *pte=00000000, *ppte=00000000
> [ 3451.272146] Internal error: Oops: 80000007 [#2] ARM
> [ 3451.277312] CPU: 0    Tainted: G      D       (3.9.0-rc8-00020-g6e8f1be-dirty #210)
> [ 3451.285411] PC is at 0x0
> [ 3451.288105] LR is at pagevec_lru_move_fn+0x90/0xe4
> [ 3451.293172] pc : [<00000000>]    lr : [<c00a00b8>]    psr: 600000b3
> [ 3451.293172] sp : cf479df4  ip : 00000040  fp : 00000000
> [ 3451.305311] r10: c05d8ebc  r9 : c0d09e00  r8 : 0000030c
> [ 3451.310834] r7 : c05b72e8  r6 : 60000013  r5 : 00000002  r4 : c05d8ebc
> [ 3451.317736] r3 : 00000001  r2 : cf478000  r1 : c05d90f0  r0 : c0d09e00
> [ 3451.324639] Flags: nZCv  IRQs off  FIQs on  Mode SVC_32  ISA Thumb  Segment user
> [ 3451.332460] Control: 10c5387d  Table: 8f468019  DAC: 00000015
> [ 3451.338535] Process sh (pid: 913, stack limit = 0xcf478238)
> [ 3451.344427] Stack: (0xcf479df4 to 0xcf47a000)

No idea, may be a memory corruption, for example. Is this reproducible?

-- 
Best Regards,
Artem Bityutskiy

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