linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: Steven Cole <elenstev@mesatop.com>
Cc: linux-mm@kvack.org
Subject: Re: 2.5.33-mm4 filemap_copy_from_user: Unexpected page fault
Date: Fri, 06 Sep 2002 09:51:19 -0700	[thread overview]
Message-ID: <3D78DD07.E36AE3A9@zip.com.au> (raw)
In-Reply-To: <1031327285.1984.155.camel@spc9.esa.lanl.gov>

Steven Cole wrote:
> 
> With 2.5.33-mm4, I tried running dbench on an ext2 partition and was
> able to run up to dbench 80 successfully.  However, at dbench 96, I got
> four messages like this:
> 
> filemap_copy_from_user: Unexpected page fault

Yep.  This means that the page we faulted in by-hand in generic_file_write()
wasn't resident during the subsequent copy_from_user().

That fault-in by-hand is there to prevent a deadlock.  That printk
meand that it isnt working all the time.   We have (always had) a
problem.

> Shortly after this, the box hung again,
> ...
> >>EIP; c0159bf4 <sync_sb_inodes+84/260>   <=====
> Trace; c0159e1e <writeback_inodes+4e/80>
> Trace; c013b8aa <background_writeout+7a/c0>
> Trace; c013b4cb <__pdflush+12b/1d0>

Hum.  Thanks for that.

I've been dbenching and compiling all night.  And yet, it
seems that the dirty inode search in sync_sb_inodes() can trivially
lock up.

Does this fix?

 fs-writeback.c |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

--- 2.5.33/fs/fs-writeback.c~scole	Fri Sep  6 09:50:25 2002
+++ 2.5.33-akpm/fs/fs-writeback.c	Fri Sep  6 09:50:47 2002
@@ -242,16 +242,16 @@ sync_sb_inodes(struct super_block *sb, s
 
 		if (wbc->nonblocking && bdi_write_congested(bdi)) {
 			wbc->encountered_congestion = 1;
+			list_move(&inode->i_list, &sb->s_dirty);
 			if (sb != blockdev_superblock)
 				break;		/* Skip the entire fs */
-			list_move(&inode->i_list, &sb->s_dirty);
 			continue;
 		}
 
 		if (wbc->bdi && bdi != wbc->bdi) {
+			list_move(&inode->i_list, &sb->s_dirty);
 			if (sb != blockdev_superblock)
 				break;		/* inappropriate superblock */
-			list_move(&inode->i_list, &sb->s_dirty);
 			continue;		/* not this blockdev */
 		}
 

.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/

  reply	other threads:[~2002-09-06 16:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-06 15:48 Steven Cole
2002-09-06 16:51 ` Andrew Morton [this message]
2002-09-06 17:03   ` Steven Cole
2002-09-06 17:36     ` Andrew Morton
2002-09-06 17:54       ` Steven Cole

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=3D78DD07.E36AE3A9@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=elenstev@mesatop.com \
    --cc=linux-mm@kvack.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