From: Alex Tomas <bzzz@tmi.comex.ru>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@digeo.com>
Subject: bash-shared-mapping oops'es on 2.5.66-mm1
Date: Sat, 19 Apr 2003 12:06:01 +0400 [thread overview]
Message-ID: <m37k9qrjx2.fsf@tmi.comex.ru> (raw)
hi!
[root@proto db2]# /root/tools/bash-shared-mapping -n 5 -t 3 foo 300000000
on serial console:
------------[ cut here ]------------
kernel BUG at mm/rmap.c:408!
invalid operand: 0000 [#1]
Program received signal SIGTRAP, Trace/breakpoint trap.
page_remove_rmap (page=0xc1345580, ptep=0xc1345580) at mm/rmap.c:408
408 BUG();
(gdb) bt
#0 page_remove_rmap (page=0xc1345580, ptep=0xc1345580) at mm/rmap.c:408
#1 0xc0143c63 in zap_pte_range (tlb=0xc03d957c, pmd=0xc9c3a478, address=1199570944, size=4194304)
at mm/memory.c:426
#2 0xc0143d45 in zap_pmd_range (tlb=0xc03d957c, dir=0xc9c3a478, address=1199570944, size=208994304)
at mm/memory.c:458
#3 0xc0143da0 in unmap_page_range (tlb=0xc03d957c, vma=0xd3cf0ee0, address=1130024960, end=1408565248)
at mm/memory.c:479
#4 0xc0143e94 in unmap_vmas (tlbp=0xcf64de74, mm=0xdf657220, vma=0xd3cf0ee0, start_addr=1130024960,
end_addr=1408565248, nr_accounted=0xcf64de78) at mm/memory.c:573
#5 0xc01441ac in zap_page_range (vma=0xd3cf0ee0, address=1130024960, size=278540288)
at mm/memory.c:618
#6 0xc0144d58 in vmtruncate_list (head=0xda8d3db0, pgoff=5240) at mm/memory.c:1065
#7 0xc0144e2f in vmtruncate (inode=0xda8d3ccc, offset=21460646) at mm/memory.c:1094
#8 0xc016d5b9 in inode_setattr (inode=0xda8d3ccc, attr=0xcf64df60) at fs/attr.c:72
#9 0xc018dab2 in ext3_setattr (dentry=0xdfcc2da0, attr=0xcf64df60) at fs/ext3/inode.c:2536
#10 0xc016d8bb in notify_change (dentry=0xdfcc2da0, attr=0xcf64df60) at fs/attr.c:163
#11 0xc0151de8 in do_truncate (dentry=0xdfcc2da0, length=21460646) at fs/open.c:90
#12 0xc0152343 in sys_ftruncate64 (fd=3, length=21460646) at fs/open.c:197
(gdb)
next reply other threads:[~2003-04-19 7:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-19 8:06 Alex Tomas [this message]
2003-04-19 8:52 ` Andrew Morton
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=m37k9qrjx2.fsf@tmi.comex.ru \
--to=bzzz@tmi.comex.ru \
--cc=akpm@digeo.com \
--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®