From: Andi Kleen <ak@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: davem@redhat.com (David S. Miller),
willy@debian.org, thunder7@xs4all.nl,
parisc-linux@lists.parisc-linux.org,
linux-kernel@vger.kernel.org
Subject: Re: [parisc-linux] documented Oops running big-endian reiserfs on parisc architecture
Date: 03 Sep 2001 09:29:12 +0200 [thread overview]
Message-ID: <oup66b0zq9j.fsf@pigdrop.muc.suse.de> (raw)
In-Reply-To: Alan Cox's message of "3 Sep 2001 01:32:44 +0200"
Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> > > Is it impossible to handle unaligned access traps properly on
> > > parisc? If so, well you have some problems...
> >
> > No, we just haven't bothered to implement it yet. Not many people
> > use IPX these days.
>
> You also need unaligned trap fixups for
>
> AX.25, NetROM, LAPB, X.25, Appletalk, PPP, Anything over 802.2LLC, Linus
> NFS code for some NFS mount options (although not the -ac NFS code)
And also everybody connected to the internet needs them, because you can
create arbitarily unaligned TCP/UDP/ICMP headers using IP option byte sized
NOPs.
-Andi
next parent reply other threads:[~2001-09-03 7:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010903002514.X5126@parcelfarce.linux.theplanet.co.uk.suse.lists.linux.kernel>
[not found] ` <E15dghq-0000bZ-00@the-village.bc.nu.suse.lists.linux.kernel>
2001-09-03 7:29 ` Andi Kleen [this message]
2001-09-03 8:15 ` [parisc-linux] documented Oops running big-endian reiserfs on parisc architecture David S. Miller
2001-09-03 8:41 ` Andi Kleen
2001-09-03 10:48 ` Hans Reiser
2001-09-03 14:31 ` Matthew Wilcox
2001-09-03 15:44 ` Horst von Brand
2001-09-02 8:55 thunder7
2001-09-02 14:00 ` Matthew Wilcox
2001-09-02 23:04 ` David S. Miller
2001-09-02 23:25 ` Matthew Wilcox
2001-09-02 23:26 ` David S. Miller
2001-09-02 23:31 ` Alan Cox
2001-09-05 1:01 ` Randolph Chung
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=oup66b0zq9j.fsf@pigdrop.muc.suse.de \
--to=ak@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=thunder7@xs4all.nl \
--cc=willy@debian.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