From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jurij Smakov Date: Sat, 21 Oct 2006 04:11:08 +0000 Subject: Unaligned accesses in compat_sys_msgrcv and sys_msgrcv Message-Id: <20061021041107.GA4629@droopy.oc.cox.net> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: sparclinux@vger.kernel.org Hi, Every time I compile anything on my box running 2.6.18, I get these messages in dmesg every 5 seconds: Kernel unaligned access at TPC[4ec2f0] sys_msgrcv+0x2dc/0x32c Kernel unaligned access at TPC[4e9f6c] compat_sys_msgrcv+0xbc/0x124 Kernel unaligned access at TPC[4ec2f0] sys_msgrcv+0x2dc/0x32c Kernel unaligned access at TPC[4e9f6c] compat_sys_msgrcv+0xbc/0x124 Kernel unaligned access at TPC[4ec2f0] sys_msgrcv+0x2dc/0x32c Decoding the addresses indicates that the unaligned accesses are generated by get_user call in compat_sys_msgrcv at ipc/compat.c:357 and put_user in sys_msgrcv at ipc/msg.c:836. As far as I can tell, the problem stems from the fact that allocating memory with p = compat_alloc_user_space(second + sizeof(struct msgbuf)); at ipc/compat.c:352 does not guarantee alignment of p, so when we later try to ldxa from the address &p->mtype (in get_user) or stxa to &msgp->mtype (in put_user), we catch an exception. As I'm not sure what would be the correct fix here, I'd appreciate any advice on how to deal with that. Best regards, -- Jurij Smakov jurij@wooyd.org Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC