Red Hat Bugzilla – Bug 132997
Signed module causes unaligned kernel access
Last modified: 2007-11-30 17:07:13 EST
Starting from 1-579 kernel, signed module causes unaligned kernel
access on ia64. I am getting
kernel unaligned access to 0xa0000002002e47ee, ip=0xa000000100211960
kernel unaligned accesses are legal and usually not a problem
I'll neuter the warning
2.6.8-1.603 still reports:
kernel unaligned access to 0xa0000002002d805e, ip=0xa0000001002112e0
kernel unaligned access to 0xa0000002002d806e, ip=0xa0000001002112e0
kernel unaligned access to 0xa0000002002d807e, ip=0xa0000001002112e0
kernel unaligned access to 0xa0000002002d808e, ip=0xa0000001002112e0
2.6.9-1.648_EL has the same problem:
kernel unaligned access to 0xa00000020039805f, ip=0xa000000100215c80
kernel unaligned access to 0xa00000020039806f, ip=0xa000000100215c80
kernel unaligned access to 0xa00000020039807f, ip=0xa000000100215c80
kernel unaligned access to 0xa00000020039808f, ip=0xa000000100215c80
I have a patch for this. The problem is that the SHA1 crypto code is given a
u8* to the buffer it is to digest, but then reads from it as u32* under certain
Situations can be contrived in which the u32* will be misaligned, either by
preloading the digest with an odd number of bytes or by passing it a pointer
that's not aligned on a 32-bit boundary.
For most archs, this shouldn't be a problem as fixing up is possible, if not
trivial; but for some archs fixing up isn't possible. So I've made the patch
fix SHA1 rather than removing the warning from IA64.
Created attachment 106966 [details]
Patch to fix SHA1's potential misaligned accesses
This patch works for me.
Fix confirmed with latest code. Closing out.
REOPENED status has been deprecated. ASSIGNED with keyword of Reopened is preferred.
closed per comment #17. If anyone would like to revisit this issue, please
reopen if need to.