linux-kernel - Re: Rootfs in eMMC: Kernel panic ...Attempted to kill init!

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: <1245680789.15580.85.camel@pc1117.cambridge.arm.com>
Date:	Mon, 22 Jun 2009 15:26:29 +0100
From:	Catalin Marinas <catalin.marinas@....com>
To:	Sudeep K N <sudeepholla.maillist@...il.com>
Cc:	Russell King - ARM Linux <linux@....linux.org.uk>,
	linux-arm-kernel@...ts.arm.linux.org.uk, drzeus-mmc@...eus.cx,
	linux-kernel@...r.kernel.org
Subject: Re: Rootfs in eMMC: Kernel panic ...Attempted to kill init!

On Mon, 2009-06-22 at 19:43 +0530, Sudeep K N wrote:
> Thanks for the suggestion.
> With the logs it is clear that crash is in the userspace.
> I am getting one of the 2 logs(below) randomly.

This sounds familiar: SMP -> writealloc cache policy (could be forced by
hardware) -> cache corruption in user space with ext2.

Does you driver use the DMA API? If not, does your eMMC driver flush the
cache (in case you hit one of the long-standing problems with PIO
drivers).

It's worth trying this hack:

http://article.gmane.org/gmane.linux.ports.arm.kernel/51556

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