From: Andrew Morton <akpm@osdl.org>
To: "David S. Miller" <davem@davemloft.net>
Cc: phdm@macqel.be, linux-kernel@vger.kernel.org, uclinux-dev@uclinux.org
Subject: Re: PATCH : ppp + big-endian = kernel crash
Date: Sun, 29 May 2005 19:52:45 -0700 [thread overview]
Message-ID: <20050529195245.33f36253.akpm@osdl.org> (raw)
In-Reply-To: <20050529.145509.82051753.davem@davemloft.net>
"David S. Miller" <davem@davemloft.net> wrote:
>
> From: "Philippe De Muyter" <phdm@macqel.be>
> Date: Sun, 29 May 2005 23:38:53 +0200 (CEST)
>
> > Do you mean that ip_rcv may not assume that packets are properly aligned ?
> >
> > And some non-mmu m68k (Coldfires) do not provide enough information in
> > exception frames to restart instructions on an address error in the general
> > case.
>
> So many variants of tunneling and protocol encapsulation can result in
> unaligned packet headers, and as a result platforms really must
> provide proper unaligned memory access handling in kernel mode in
> order to use the networking fully.
As Philippe mentioned, old 68k's simply cannot do this.
> All these patches to PPP and friends are merely papering over the
> larger problem.
It's not a thing we want to do in the general case, sure. But it's
reasonable to identify those bits of net code which the nommu people care
about and look to see if there's some sane workaround to get them going.
Otherwise, things like PPP will simply unavailable to some architectures...
next prev parent reply other threads:[~2005-05-30 2:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-29 19:48 Philippe De Muyter
2005-05-29 20:52 ` David S. Miller
2005-05-29 21:38 ` Philippe De Muyter
2005-05-29 21:55 ` David S. Miller
2005-05-30 2:52 ` Andrew Morton [this message]
2005-05-30 3:11 ` David S. Miller
2005-06-01 15:26 ` Philippe De Muyter
2005-05-30 10:22 ` Andi Kleen
2005-05-30 13:01 ` cutaway
2005-05-30 7:16 ` Giuliano Pochini
2005-05-30 14:05 Greg Ungerer
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=20050529195245.33f36253.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=phdm@macqel.be \
--cc=uclinux-dev@uclinux.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®