From: Andrew Morton <akpm@osdl.org>
To: "Sergey S. Kostyliov" <rathamahata@php4.ru>
Cc: linux-kernel@vger.kernel.org, reiserfs-list@namesys.com
Subject: Re: 2.6.0-testX and InnoDB (was: Re: 2.6.0-test2-mm3 and mysql)
Date: Sun, 31 Aug 2003 12:06:48 -0700 [thread overview]
Message-ID: <20030831120648.7c5eed6e.akpm@osdl.org> (raw)
In-Reply-To: <200308311437.51942.rathamahata@php4.ru>
"Sergey S. Kostyliov" <rathamahata@php4.ru> wrote:
>
> fsx-linux hasn't been producing any error messages or logs since Friday.
> But I've got an oops. Here it is.
>
> ksymoops 2.4.9 on i686 2.6.0-test4. Options used
> -V (default)
> -K (specified)
> -l /proc/modules (default)
> -o /lib/modules/2.6.0-test4/ (default)
> -m /proc/kallsyms (specified)
>
> No modules in ksyms, skipping objects
> No ksyms, skipping lsmod
> 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
> 0000:00:0c.0: 3Com PCI 3c905 Boomerang 100baseTx at 0xb800. Vers LK1.1.19
> kernel BUG at mm/filemap.c:336!
> invalid operand: 0000 [#1]
> CPU: 0
> EIP: 0060:[<c01324f0>] Not tainted
> Using defaults from ksymoops -t elf32-i386 -a i386
> EFLAGS: 00010246
> eax: 00000000 ebx: c1577e70 ecx: 00000016 edx: 00000001
> esi: c1a00448 edi: d5f3e820 ebp: e7147858 esp: c1bbbd34
> ds: 007b es: 007b ss: 0068
> Stack: c1577e70 00000286 00000000 c0191a4e c1577e70 eb14fde0 d5f3e850 c1577e70
> 00000000 00000000 00000000 e7147904 c1577e70 c1bbbe64 e71478e4 c013c294
> c1577e70 c1bbbdac c1bba000 c1bba000 c1bba000 c1bba000 c1bba000 c1bba000
> Call Trace:
> [<c0191a4e>] reiserfs_write_full_page+0xee/0x3a0
> [<c013c294>] shrink_list+0x394/0x5f0
> [<c013afe8>] __pagevec_release+0x28/0x40
> [<c013c6a7>] shrink_cache+0x1b7/0x350
> [<c013d267>] balance_pgdat+0x187/0x220
> [<c013d443>] kswapd+0x143/0x150
> [<c01183b0>] autoremove_wake_function+0x0/0x50
> [<c0109232>] ret_from_fork+0x6/0x14
> [<c01183b0>] autoremove_wake_function+0x0/0x50
> [<c013d300>] kswapd+0x0/0x150
You need this:
diff -puN fs/reiserfs/inode.c~reiserfs-writepage-fix fs/reiserfs/inode.c
--- 25/fs/reiserfs/inode.c~reiserfs-writepage-fix 2003-08-26 10:12:14.000000000 -0700
+++ 25-akpm/fs/reiserfs/inode.c 2003-08-26 10:12:14.000000000 -0700
@@ -2048,8 +2048,8 @@ static int reiserfs_write_full_page(stru
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-08-31 19:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-03 0:38 2.6.0-test2-mm3 and mysql Shane Shrybman
2003-08-03 1:04 ` Andrew Morton
2003-08-03 1:52 ` Con Kolivas
2003-08-03 1:59 ` Andrew Morton
2003-08-03 1:58 ` Shane Shrybman
2003-08-03 2:08 ` Andrew Morton
2003-08-03 15:01 ` Shane Shrybman
2003-08-03 19:25 ` Andrew Morton
2003-08-03 18:58 ` Sergey S. Kostyliov
2003-08-04 0:05 ` Matt Mackall
2003-08-27 15:52 ` Sergey S. Kostyliov
2003-08-28 16:15 ` 2.6.0-testX and InnoDB (was: Re: 2.6.0-test2-mm3 and mysql) Sergey S. Kostyliov
2003-08-28 19:50 ` Andrew Morton
2003-08-29 8:12 ` Sergey S. Kostyliov
2003-08-31 10:37 ` Sergey S. Kostyliov
2003-08-31 19:06 ` Andrew Morton [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=20030831120648.7c5eed6e.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rathamahata@php4.ru \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).