From: Will Simoneau <simoneau@ele.uri.edu>
To: sparclinux@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: [sparc64] 2.6.18 unaligned accesses in eth1394
Date: Thu, 5 Oct 2006 17:15:44 -0400 [thread overview]
Message-ID: <20061005211543.GA18539@ele.uri.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1300 bytes --]
Here's a pair of unaligned accesses I found playing with the eth1394 driver:
Kernel unaligned access at TPC[102c8190] ether1394_tx+0xf8/0x600 [eth1394]
Kernel unaligned access at TPC[10162c8c] ether1394_data_handler+0x914/0x1000 [eth1394]
The first one I seem to be able to fix by adding a get_unaligned() at
lines 1679-1680 of eth1394.c around eth->h_dest; the second one seems to
be triggered by this code:
(gdb) list *ether1394_data_handler+0x914
0xc94 is in ether1394_data_handler (drivers/ieee1394/eth1394.c:1264).
1259 priv->stats.rx_dropped++;
1260 dev_kfree_skb_any(skb);
1261 goto bad_proto;
1262 }
1263
1264 if (netif_rx(skb) == NET_RX_DROP) {
1265 priv->stats.rx_errors++;
1266 priv->stats.rx_dropped++;
1267 goto bad_proto;
1268 }
Unaligned accesses caused by netif_rx seem to have happened before on
mips long ago (according to google). I suspect nobody has ever tried
eth1394 on sparc64 ;-)
eth1394 seems to work fine otherwise, I can plug a firewire hdd and a
laptop with firewire into the sparc and everything works OK. I get
~13MB/sec network throughput from laptop -> sparc (the sparc's CPU is
hitting 100% system time), I suspect it would be a lot faster with the
alignment problem fixed.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2006-10-05 21:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-05 21:15 Will Simoneau [this message]
2006-10-05 22:22 ` [sparc64] 2.6.18 unaligned accesses in eth1394 David Miller
2006-10-10 1:36 ` David Miller
2006-10-10 13:29 ` Will Simoneau
2006-10-10 22:17 ` David Miller
2006-10-11 12:33 ` Stefan Richter
2006-10-28 0:12 ` David Miller
2006-10-28 6:46 ` Stefan Richter
2006-10-12 14:37 ` Will Simoneau
2006-10-12 21:34 ` David Miller
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=20061005211543.GA18539@ele.uri.edu \
--to=simoneau@ele.uri.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@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