linux-kernel - Re: kernel unaligned accesses on 2.6.29.

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] [day] [month] [year] [list]

Message-Id: <20090324.190414.59071734.davem@davemloft.net>
Date:	Tue, 24 Mar 2009 19:04:14 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	holt@....com
Cc:	chuck.lever@...cle.com, tony.luck@...el.com,
	linux-ia64@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: kernel unaligned accesses on 2.6.29.

From: Robin Holt <holt@....com>
Date: Tue, 24 Mar 2009 20:14:18 -0500

> You either need to use memcpy, or not define it as an unsigned char.
> Tony, any suggestions?

memcpy() might not work in this scenerio.

GCC can still emit an inline 64-bit memory access if it
deems that the objects involved should be sufficiently
aligned.

It might not be able to in this specific case, but it is
something to be aware of.  Don't be convinced of any fix
for this until the assembler is inspected by hand :-)
--
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/