On Mon, May 23, 2011 at 12:16:48PM +0100, Catalin Marinas wrote:
Newer versions of gcc generate unaligned accesses by default, causing
kernel panics when CONFIG_ALIGNMENT_TRAP is enabled. This patch adds the
-mno-unaligned-access option to gcc.
This description doesn't make sense. If we have alignment traps enabled,
then we _expect_ to fix up unaligned loads and stores.
Therefore there should be no panic if CONFIG_ALIGNMENT_TRAP is enabled.
So what's the _actual_ problem that this is trying to address? What's
the panic/oops look like? And that information should be in the commit
description _anyway_.