David Miller wrote: > From: Joerg Friedrich > Date: Fri, 30 Mar 2007 23:48:57 +0200 > > >>I wanted to use the iptables ULOG target, but I ran into these error >>messages. can anyone explain howto read this messge. >> >>Kernel unaligned access at TPC[1029e35c] ipt_ulog_packet+0x214/0x3fc [ipt_ULOG] > > > It just means that unaligned accesses are occuring in the ipt_ulog > module. Things usually work fine when this happens, just very slowly, > which is why the warning is printed. > > Patrick, this is on sparc64, it appears to be this code: > > pm->timestamp_sec = skb->tstamp.off_sec; > pm->timestamp_usec = skb->tstamp.off_usec; > > and the NLMSG_DATA() (and thus 'pm') is not 8-byte aligned. > > I bet this is a 32-bit sparc binary, has the idea of a compat > layer for the ULOG bits ever been discussed? No, I can't imagine how to do this since we don't have any compat infrastructure for netlink, so we would have to know whether the receiving process is a 32 bit binary in ipt_ULOG itself. We have some compat code in userspace to deal with the different structure layout, so besides the unaligned accesses, it should already work fine. Since ULOG is obsolete and nfnetlink_log shouldn't have these issues, I think the best way to fix this is to use put_unaligned in ipt_ULOG. How does this look?