public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@debian.org>
To: thunder7@xs4all.nl
Cc: 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: Sun, 2 Sep 2001 15:00:23 +0100	[thread overview]
Message-ID: <20010902150023.U5126@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20010902105538.A15344@middle.of.nowhere>
In-Reply-To: <20010902105538.A15344@middle.of.nowhere>; from thunder7@xs4all.nl on Sun, Sep 02, 2001 at 10:55:38AM +0200

On Sun, Sep 02, 2001 at 10:55:38AM +0200, thunder7@xs4all.nl wrote:
> ReiserFS version 3.6.25
> bonnie[163]: Unaligned data reference 28

As it says, an unaligned data reference.

> r0-3     00000000 102ec550 10197d0c 26f24838

> IASQ: 00000000 00000000 IAOQ: 10197d10 10197d14

In kernel mode.

> 10197d10:       0c 7c 10 93     ldw  e(sr0,r3),r19

r3 is 26f24838, and offset `e' from that is unaligned.

> which makes the error somewhere around here in 
> fs/reiserfs/namei.c, function reiserfs_add_entry, after call to
> padd_item, before call to reiserfs_find_entry:
> 
>     /* copy name */
>     memcpy ((char *)(deh + 1), name, namelen);
>     /* padd by 0s to the 4 byte boundary */
>     padd_item ((char *)(deh + 1), ROUND_UP (namelen), namelen);
> 
>     /* entry is ready to be pasted into tree, set 'visibility' and 'stat data in entry' attributes */
>     mark_de_without_sd (deh);
>     visible ? mark_de_visible (deh) : mark_de_hidden (deh);
> 
>     /* find the proper place for the new entry */
>     memset (bit_string, 0, sizeof (bit_string));
>     de.de_gen_number_bit_string = (char *)bit_string;
>     retval = reiserfs_find_entry (dir, name, namelen, &path, &de);

I suspect mark_de_without_sd is an inlined function/macro and this will
be where the unaligned data reference is happening.

-- 
Revolutions do not require corporate support.

  reply	other threads:[~2001-09-02 14:00 UTC|newest]

Thread overview: 20+ 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 ` Matthew Wilcox [this message]
2001-09-02 17:57   ` [SOLVED + PATCH]: " thunder7
2001-09-02 22:34     ` Richard Zidlicky
2001-09-02 23:08       ` David S. Miller
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
     [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   ` [parisc-linux] " Andi Kleen
2001-09-03  8:15     ` 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

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=20010902150023.U5126@parcelfarce.linux.theplanet.co.uk \
    --to=willy@debian.org \
    --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