From: Ralf Baechle <ralf@linux-mips.org>
To: Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-hams@vger.kernel.org,
Simon Eatough <simon.eatough@gmail.com>
Subject: Unaligned accesses in AVR32 kernel
Date: Wed, 3 Nov 2010 15:32:06 +0000 [thread overview]
Message-ID: <20101103153206.GA20830@linux-mips.org> (raw)
Hans-Christian,
I received a bug report for some networking code from which it seems as
if the AVR32 kernel doesn't fixup exceptions caused by missaligned kernel
accesses either in software or hardware. This is a problem as there in
the networking stack there is no general guarantee that all multi-byte
header fields such as ARP or IP headers will aligned. Networking drivers
are supposed to make a decent attempt to place packets at a suitable
address but there is no guarantee. The mkiss.c driver gets that wrong
which I'm fixing but fundamentally you want to add automated fixing of
unaligned exception to the AVR32 kernel. See arch/mips/kernel/unaligned.c.
Cheers,
Ralf
reply other threads:[~2010-11-03 15:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20101103153206.GA20830@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=hans-christian.egtvedt@atmel.com \
--cc=linux-hams@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=simon.eatough@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).