From: Oleg Drokin <green@namesys.com>
To: Alexander Vodomerov <alex@sectorb.msk.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: sync crashed with segfault on 2.6.0-test4 (reiserfs partition)
Date: Mon, 8 Sep 2003 12:54:33 +0400 [thread overview]
Message-ID: <20030908085433.GB17718@namesys.com> (raw)
In-Reply-To: <200309051424.48834.alex@sectorb.msk.ru>
Hello!
On Fri, Sep 05, 2003 at 02:24:48PM +0400, Alexander Vodomerov wrote:
> Yesterday I've tried 2.6.0-test4 kernel. It works fine about 17 hours, but
> suddenly sync command causes a segfault. I've made sync many times
> Sep 4 16:43:36 lorien kernel: EIP: 0060:[mpage_writepages+301/688]
> Sep 4 16:43:36 lorien kernel: [reiserfs_writepage+0/64] reiserfs_writepage+0x0/0x40
> Sep 4 16:43:36 lorien kernel: [do_writepages+54/64] do_writepages+0x36/0x40
> Sep 4 16:43:36 lorien kernel: [__sync_single_inode+169/496] __sync_single_inode+0xa9/0x1f0
> Sep 4 16:43:36 lorien kernel: [sync_sb_inodes+396/560] sync_sb_inodes+0x18c/0x230
> Sep 4 16:43:36 lorien kernel: [sync_inodes_sb+119/144] sync_inodes_sb+0x77/0x90
> Sep 4 16:43:36 lorien kernel: [sync_inodes+43/160] sync_inodes+0x2b/0xa0
> Sep 4 16:43:36 lorien kernel: [do_sync+35/112] do_sync+0x23/0x70
> Sep 4 16:43:36 lorien kernel: [sys_sync+15/32] sys_sync+0xf/0x20
> Sep 4 16:43:36 lorien kernel: [syscall_call+7/11] syscall_call+0x7/0xb
This is fixed in current bk tree/current -mm tree.
The following patch should do the trick.
Bye,
Oleg
diff -Nru a/fs/reiserfs/inode.c b/fs/reiserfs/inode.c
--- a/fs/reiserfs/inode.c Mon Sep 8 12:54:12 2003
+++ b/fs/reiserfs/inode.c Mon Sep 8 12:54:12 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) ;
prev parent reply other threads:[~2003-09-08 8:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-05 10:24 Alexander Vodomerov
2003-09-08 8:54 ` Oleg Drokin [this message]
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=20030908085433.GB17718@namesys.com \
--to=green@namesys.com \
--cc=alex@sectorb.msk.ru \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®