From: Sachin Sant <sachinp@in.ibm.com>
To: linux-fsdevel@vger.kernel.org
Cc: Al Viro <viro@zeniv.linux.org.uk>,
linux-s390@vger.kernel.org, linux-next@vger.kernel.org,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [-next Feb 8] kernel BUG at fs/dcache.c:676!
Date: Thu, 11 Feb 2010 10:43:02 +0530 [thread overview]
Message-ID: <4B7391DE.1070200@in.ibm.com> (raw)
In-Reply-To: <4B7028BD.9070108@in.ibm.com>
Sachin Sant wrote:
> While running hackbench against today's next-20100208 (9056d31..)
> on a s390 box, came across following BUG.
>
I can still recreate this issue against next-20100210.
kjournald starting. Commit interval 5 seconds
EXT3-fs (dasdb1): using internal journal
EXT3-fs (dasdb1): mounted filesystem with writeback data mode
BUG: Dentry 00000000fbde0ec0{i=13c39,n=bin} still in use (1) unmount of ext3 da
sdb1
------------ cut here ------------
kernel BUG at fs/dcache.c:676!
illegal operation: 0001 #1 SMP
Modules linked in: fuse loop zfcp qeth_l3 scsi_transport_fc ipv6 scsi_tgt vmur s
csi_mod ext3 jbd mbcache dasd_eckd_mod dasd_fba_mod dasd_mod qeth qdio ccwgroup
dm_mod
CPU: 1 Not tainted 2.6.33-rc7-autotest-next-20100210-5-default #1
Process umount (pid: 2125, task: 00000000fac04138, ksp: 00000000fb58bb80)
Krnl PSW : 0704100180000000 000000000023ef1c (shrink_dcache_for_umount_subtree+0
x3a8/0x3d0)
R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:0 CC:1 PM:0 EA:3
Krnl GPRS: 0000000000010000 0000000000686648 000000000000005c 00000000fffffffe
0000000000449fa2 0000000000000000 0000000000000001 0000000000000001
00000000000000e0 000000000060ba00 00000000fbde0e60 0000000000623218
00000000fac18e68 000000000046efc0 000000000023ef18 00000000fb58bcf8
Krnl Code: 000000000023ef0c: e3c0f0a80024 stg %r12,168(%r15)
000000000023ef12: c0e50010581f brasl %r14,449f50
000000000023ef18: a7f40001 brc 15,23ef1a
>000000000023ef1c: a7f40000 brc 15,23ef1c
000000000023ef20: c0b0001f217c larl %r11,623218
000000000023ef26: a7f4fe79 brc 15,23ec18
000000000023ef2a: c020001e656b larl %r2,60ba00
000000000023ef30: c0e5000722a8 brasl %r14,323480
Call Trace:
( <000000000023ef18>¨ shrink_dcache_for_umount_subtree+0x3a4/0x3d0)
<000000000023efa6>¨ shrink_dcache_for_umount+0x62/0x98
<000000000022a1fc>¨ generic_shutdown_super+0x3c/0x160
<000000000022a356>¨ kill_block_super+0x36/0x54
<000000000022ad00>¨ deactivate_super+0xa0/0xc8
<0000000000247826>¨ SyS_umount+0x72/0x404
<0000000000118bae>¨ sysc_noemu+0x10/0x16
<0000020000149836>¨ 0x20000149836
Last Breaking-Event-Address:
<000000000023ef18>¨ shrink_dcache_for_umount_subtree+0x3a4/0x3d0
> kjournald starting. Commit interval 5 seconds
> EXT3-fs (dasdb1): using internal journal
> EXT3-fs (dasdb1): mounted filesystem with writeback data mode
> BUG: Dentry 00000000fc937d40{i=13c39,n=bin} still in use (1) Ýunmount
> of ext3 da
> sdb1¨
> ------------" cut here "------------
> kernel BUG at fs/dcache.c:676!
> illegal operation: 0001 "#1" SMP
> Modules linked in: fuse loop zfcp scsi_transport_fc qeth_l3 scsi_tgt
> ipv6 vmur s
> csi_mod ext3 jbd mbcache dasd_eckd_mod dasd_fba_mod dasd_mod qeth qdio
> ccwgroup
> dm_mod
> CPU: 2 Not tainted 2.6.33-rc7-autotest-next-20100208-5-default #1
> Process umount (pid: 2120, task: 00000000fb3da538, ksp: 00000000fc6c7b80)
> Krnl PSW : 0704100180000000 000000000023ef54
> (shrink_dcache_for_umount_subtree+0
> x3a8/0x3d0)
> R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:0 CC:1 PM:0 EA:3
> Krnl GPRS: 0000000000010000 0000000000686648 000000000000005c
> 00000000fffffffd
> 0000000000448a52 0000000000000000 0000000000000001
> 0000000000000001
> 00000000000000e0 000000000060ba00 00000000fc937ce0
> 0000000000623218
> 00000000fae10e68 000000000046ced8 000000000023ef50
> 00000000fc6c7cf8
> Krnl Code: 000000000023ef44: e3c0f0a80024 stg %r12,168(%r15)
> 000000000023ef4a: c0e500104d5b brasl %r14,448a00
> 000000000023ef50: a7f40001 brc 15,23ef52
> >000000000023ef54: a7f40000 brc 15,23ef54
> 000000000023ef58: c0b0001f2160 larl %r11,623218
> 000000000023ef5e: a7f4fe79 brc 15,23ec50
> 000000000023ef62: c020001e654f larl %r2,60ba00
> 000000000023ef68: c0e50007229c brasl %r14,3234a0
> Call Trace:
> (<000000000023ef50> shrink_dcache_for_umount_subtree+0x3a4/0x3d0)
> <000000000023efde> shrink_dcache_for_umount+0x62/0x98
> <000000000022a234> generic_shutdown_super+0x3c/0x160
> <000000000022a38e> kill_block_super+0x36/0x54
> <000000000022ad38> deactivate_super+0xa0/0xc8
> <000000000024785e> SyS_umount+0x72/0x404
> <0000000000118c26> sysc_noemu+0x10/0x16
> <0000020000149836> 0x20000149836
> Last Breaking-Event-Address:
> "<000000000023ef50>" shrink_dcache_for_umount_subtree+0x3a4/0x3d0
>
> Did not observe this with next-20100205. Also there doesn't seem to be
> any patches applied to this code after the last release. So not
> sure what could have caused this. Corresponding code is :
>
> 664 if (atomic_read(&dentry->d_count) != 0) {
> 665 printk(KERN_ERR
> 666 "BUG: Dentry %p{i=%lx,n=%s}"
> 667 " still in use (%d)"
> 668 " [unmount of %s %s]\n",
> 669 dentry,
> 670 dentry->d_inode ?
> 671 dentry->d_inode->i_ino : 0UL,
> 672 dentry->d_name.name,
> 673 atomic_read(&dentry->d_count),
> 674 dentry->d_sb->s_type->name,
> 675 dentry->d_sb->s_id);
> 676 BUG();
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 677 }
>
> Let me know if i can provide any other information. Have attached
> the config.
>
> Thanks
> -Sachin
>
>
--
---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2010-02-11 5:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-08 15:07 [-next Feb 8] kernel BUG at fs/dcache.c:676! Sachin Sant
2010-02-11 5:13 ` Sachin Sant [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=4B7391DE.1070200@in.ibm.com \
--to=sachinp@in.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.