All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Drokin <green@namesys.com>
To: Lorenzo Allegrucci <l.allegrucci@tiscali.it>
Cc: reiserfs-list@namesys.com
Subject: Re: 2.6.0-test4 reiserfs oops
Date: Tue, 26 Aug 2003 14:38:51 +0400	[thread overview]
Message-ID: <20030826103851.GA14676@namesys.com> (raw)
In-Reply-To: <200308261146.47241.l.allegrucci@tiscali.it>

Hello!

On Tue, Aug 26, 2003 at 11:46:47AM +0000, Lorenzo Allegrucci wrote:
> > > I have got this oops running fsstress and fsx-linux
> > > on a 20Gb reiserfs partition.  Fully reproducible.
> > What are the options to fsx and fsstress?
> fsx-linux linux-2.5.0.tar.bz2 :)
> mkdir d
> fsstress -d d -n 1000000 -p 10
> The oops follows immediately.

works for me without any patches.
Do you have SMP? Some other system details?

> > Also I immediately see a place that can lead to an oops you quoted,
> > can you try to run with the patch attached and see if the oops go away?
> The oops goes away but fsx-linux hangs in "D" state.

Ah.
I see, we need to unlock the page. How about this patch instead?

Bye,
    Oleg
===== fs/reiserfs/inode.c 1.81 vs edited =====
--- 1.81/fs/reiserfs/inode.c	Tue Aug 19 09:42:17 2003
+++ edited/fs/reiserfs/inode.c	Tue Aug 26 14:27:32 2003
@@ -2048,8 +2048,8 @@
         last_offset = inode->i_size & (PAGE_CACHE_SIZE - 1) ;
 	/* no file contents in this page */
 	if (page->index >= end_index + 1 || !last_offset) {
-	    error = 0 ;
-	    goto done ;
+    	    unlock_page(page);
+	    return 0;
 	}
 	kaddr = kmap_atomic(page, KM_USER0);
 	memset(kaddr + last_offset, 0, PAGE_CACHE_SIZE-last_offset) ;

  reply	other threads:[~2003-08-26 10:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-25 20:47 2.6.0-test4 reiserfs oops Lorenzo Allegrucci
2003-08-26  8:32 ` Oleg Drokin
2003-08-26 11:46   ` Lorenzo Allegrucci
2003-08-26 10:38     ` Oleg Drokin [this message]
2003-08-26 15:59       ` Lorenzo Allegrucci
2003-08-27  6:46         ` Oleg Drokin

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=20030826103851.GA14676@namesys.com \
    --to=green@namesys.com \
    --cc=l.allegrucci@tiscali.it \
    --cc=reiserfs-list@namesys.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.