From: David Miller <davem@davemloft.net>
To: drraid@gmail.com
Cc: linux-kernel@vger.kernel.org, kaber@trash.net
Subject: Re: Kernel 2.6.20.4 Unaligned address
Date: Fri, 13 Apr 2007 16:35:21 -0700 (PDT) [thread overview]
Message-ID: <20070413.163521.45883605.davem@davemloft.net> (raw)
In-Reply-To: <1f8291090704101602q41e30a7doe79f3606643b628b@mail.gmail.com>
From: "doctor raid" <drraid@gmail.com>
Date: Tue, 10 Apr 2007 16:02:01 -0700
> [1] kernel errors reporting unaligned access of memory
> [2] The following two lines iterate twice a piece, about once every 2 minutes:
>
> Kernel unaligned access at TPC[79c344] arpt_do_table+0x3cc/0x640
> Kernel unaligned access at TPC[79c33c] arpt_do_table+0x3c4/0x640
This patch below should fix this problem.
Patrick I'm going to push this to Linus. Even if it doesn't
fix this person's problem, either both the input device loop
and the output device loop should use the "long" casting
optimization or both should not :-)
Signed-off-by: David S. Miller <davem@davemloft.net>
diff --git a/net/ipv4/netfilter/arp_tables.c b/net/ipv4/netfilter/arp_tables.c
index 5170f5c..57b0221 100644
--- a/net/ipv4/netfilter/arp_tables.c
+++ b/net/ipv4/netfilter/arp_tables.c
@@ -166,13 +166,9 @@ static inline int arp_packet_match(const struct arphdr *arphdr,
return 0;
}
- for (i = 0, ret = 0; i < IFNAMSIZ/sizeof(unsigned long); i++) {
- unsigned long odev;
- memcpy(&odev, outdev + i*sizeof(unsigned long),
- sizeof(unsigned long));
- ret |= (odev
- ^ ((const unsigned long *)arpinfo->outiface)[i])
- & ((const unsigned long *)arpinfo->outiface_mask)[i];
+ for (i = 0, ret = 0; i < IFNAMSIZ; i++) {
+ ret |= (outdev[i] ^ arpinfo->outiface[i])
+ & arpinfo->outiface_mask[i];
}
if (FWINV(ret != 0, ARPT_INV_VIA_OUT)) {
next prev parent reply other threads:[~2007-04-13 23:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-10 23:02 doctor raid
2007-04-10 23:06 ` David Miller
2007-04-11 6:35 ` Mathieu Chouquet-Stringer
2007-04-13 23:35 ` David Miller [this message]
2007-04-14 17:16 ` Patrick McHardy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070413.163521.45883605.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=drraid@gmail.com \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®