public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <mason@suse.com>
To: Thomas Schlichter <schlicht@uni-mannheim.de>, green@namesys.com
Cc: "Barry K. Nathan" <barryn@pobox.com>,
	Andrew Morton <akpm@osdl.org>,
	Nick Piggin <piggin@cyberone.com.au>,
	linux-kernel@vger.kernel.org
Subject: Re: [BUG] heavy disk access sometimes freezes 2.5.73-mm[123]
Date: 07 Jul 2003 13:33:13 -0400	[thread overview]
Message-ID: <1057599193.20904.1352.camel@tiny.suse.com> (raw)
In-Reply-To: <200307071758.45702.schlicht@uni-mannheim.de>

On Mon, 2003-07-07 at 11:58, Thomas Schlichter wrote:
> On Monday 07 July 2003 05:30, Barry K. Nathan wrote:
> > On Sun, Jul 06, 2003 at 07:37:22PM -0700, Andrew Morton wrote:
> > > Nick Piggin <piggin@cyberone.com.au> wrote:
> > >
> > > Barry says the problem started with 2.5.73-mm1.  There was a reiserfs
> > > patch added in that kernel.
> > >
> > > Does a `patch -R' of this fix it up?
> >
> > [patch snipped]
> >
> > Yes, backing that patch out fixes it.
> 
> I had similar problems with my reiserfs root FS. For me backing out only the 
> second chunk of the patch made it, too. I've attached the patch I used for 
> that. If someone sees something really bad I'm doing with this please write, 
> because I'm playing with my root FS... ;-)

> diff -u linux-2.5.74-mm2/fs/reiserfs/tail_conversion.c.orig linux-2.5.74-mm2/fs/reiserfs/tail_conversion.c
> --- linux-2.5.74-mm2/fs/reiserfs/tail_conversion.c.orig	2003-06-23 09:26:10.000000000 -0700
> +++ linux-2.5.74-mm2/fs/reiserfs/tail_conversion.c	2003-06-23 09:26:10.000000000 -0700
> @@ -190,9 +190,6 @@ unmap_buffers(struct page *page, loff_t 
>          }
>  	bh = next ;
>        } while (bh != head) ;
> -      if ( PAGE_SIZE == bh->b_size ) {
> -	ClearPageDirty(page);
> -      }
>      }
>    } 
>  }

Heh, you read my mind.  It makes more sense for this hunk to be causing
problems than the first one.  Still we should be allowed to clear the
dirty bit since we've cleaned all the buffers on the page.

-chris



  reply	other threads:[~2003-07-07 17:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-03  9:05 [BUG] heavy disk access sometimes freezes 2.5.73-mm[123] Barry K. Nathan
2003-07-06 20:46 ` Barry K. Nathan
2003-07-07  2:27   ` Nick Piggin
2003-07-07  2:37     ` Andrew Morton
2003-07-07  3:30       ` Barry K. Nathan
2003-07-07 15:58         ` Thomas Schlichter
2003-07-07 17:33           ` Chris Mason [this message]
2003-07-07 19:18             ` Andrew Morton
2003-07-07 23:47               ` Barry K. Nathan

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=1057599193.20904.1352.camel@tiny.suse.com \
    --to=mason@suse.com \
    --cc=akpm@osdl.org \
    --cc=barryn@pobox.com \
    --cc=green@namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=piggin@cyberone.com.au \
    --cc=schlicht@uni-mannheim.de \
    /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