From: "David S. Miller" <davem@redhat.com>
To: Richard.Zidlicky@stud.informatik.uni-erlangen.de
Cc: thunder7@xs4all.nl, parisc-linux@lists.parisc-linux.org,
linux-kernel@vger.kernel.org
Subject: Re: [SOLVED + PATCH]: documented Oops running big-endian reiserfs on parisc architecture
Date: Sun, 02 Sep 2001 16:08:59 -0700 (PDT) [thread overview]
Message-ID: <20010902.160859.104033892.davem@redhat.com> (raw)
In-Reply-To: <20010903003437.A385@linux-m68k.org>
In-Reply-To: <20010902150023.U5126@parcelfarce.linux.theplanet.co.uk> <20010902195717.A21209@middle.of.nowhere> <20010903003437.A385@linux-m68k.org>
From: Richard Zidlicky <Richard.Zidlicky@stud.informatik.uni-erlangen.de>
Date: Mon, 3 Sep 2001 00:34:37 +0200
On Sun, Sep 02, 2001 at 07:57:17PM +0200, thunder7@xs4all.nl wrote:
> /* 64 bit systems (and the S/390) need to be aligned explicitly -jdm */
> -#if BITS_PER_LONG == 64 || defined(__s390__)
> +#if BITS_PER_LONG == 64 || defined(__s390__) || defined(__hppa__)
> # define ADDR_UNALIGNED_BITS (3)
> #endif
couldn't reiserfs use asm/unaligned.h like anyone else?
Seems at least sparc and mips may need the same treatment.
Sparc will act correctly for unaliagned accesses.
It will trap and run very slowly, but it wont' OOPS and
it will give correct results.
This is actually required behavior, I don't know why parisc
is acting differently.
Later,
David S. Miller
davem@redhat.com
next prev parent reply other threads:[~2001-09-02 23:10 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-02 8:55 documented Oops running big-endian reiserfs on parisc architecture thunder7
2001-09-02 14:00 ` [parisc-linux] " Matthew Wilcox
2001-09-02 17:57 ` [SOLVED + PATCH]: " thunder7
2001-09-02 22:34 ` Richard Zidlicky
2001-09-02 23:08 ` David S. Miller [this message]
2001-09-02 23:29 ` [parisc-linux] Re: [SOLVED + PATCH]: documented Oops running big-endian reiserfs Alan Cox
2001-09-04 1:38 ` [SOLVED + PATCH]: documented Oops running big-endian reiserfs on parisc architecture Jeff Mahoney
2001-09-02 23:04 ` [parisc-linux] " 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-03 10:52 ` thunder7
2001-09-03 10:25 ` Hans Reiser
2001-09-03 14:30 ` [parisc-linux] " Matthew Wilcox
-- strict thread matches above, loose matches on Subject: below --
2001-09-03 12:08 [SOLVED + PATCH]: " Ulrich Weigand
2001-09-03 13:14 ` Ralf Baechle
2001-09-03 22:24 ` David S. Miller
2001-09-08 1:41 ` Linus Torvalds
[not found] <20010902105538.A15344@middle.of.nowhere.suse.lists.linux.kernel>
[not found] ` <20010902150023.U5126@parcelfarce.linux.theplanet.co.uk.suse.lists.linux.kernel>
[not found] ` <20010902195717.A21209@middle.of.nowhere.suse.lists.linux.kernel>
[not found] ` <20010903003437.A385@linux-m68k.org.suse.lists.linux.kernel>
[not found] ` <20010903213835.A13887@fury.csh.rit.edu.suse.lists.linux.kernel>
2001-09-04 9:44 ` Andi Kleen
2001-09-04 10:04 ` David S. Miller
2001-09-04 10:25 ` Andi Kleen
2001-09-04 10:29 ` David S. Miller
2001-09-04 12:50 ` Jeff Mahoney
2001-09-04 14:34 Ulrich Weigand
2001-09-04 15:02 ` Richard B. Johnson
2001-09-04 16:09 ` John Alvord
2001-09-04 17:04 Ulrich Weigand
2001-09-04 22:55 Ulrich Weigand
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=20010902.160859.104033892.davem@redhat.com \
--to=davem@redhat.com \
--cc=Richard.Zidlicky@stud.informatik.uni-erlangen.de \
--cc=linux-kernel@vger.kernel.org \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=thunder7@xs4all.nl \
/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