From: "Mehmet Giritli" <mgiritli@giritli.eu>
To: Ian Kent <raven@themaw.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-fsdevel@vger.kernel.org, Nick Piggin <npiggin@kernel.dk>,
Al Viro <viro@zeniv.linux.org.uk>,
bugzilla-daemon@bugzilla.kernel.org
Subject: Re: [Bug 30882] Automatic process group scheduling causes crashes after a while
Date: Wed, 16 Mar 2011 19:47:14 +0200 [thread overview]
Message-ID: <1300297634.6144.6.camel@mordor> (raw)
In-Reply-To: <1300290279.2750.153.camel@perseus>
Ian,
Well, here is a copy-paste of the crash that I am seeing *everytime at
shutdown* now that I am running with your patch. It is pretty much
identical to the older ones..except that I see this at every time,
instead of just rare crashes...
Now I am going to revert your patch and check for changes in the
frequency of the crashes...
Mar 16 18:49:27 mordor kernel: [ 5696.670114] BUG: Dentry
ffff88015007f300{i=2,n=donkey} still in use (1) [unmount of nfs 0:f]
Mar 16 18:49:27 mordor kernel: [ 5696.670134] ------------[ cut
here ]------------
Mar 16 18:49:27 mordor kernel: [ 5696.670187] kernel BUG at
fs/dcache.c:943!
Mar 16 18:49:27 mordor kernel: [ 5696.670237] invalid opcode: 0000 [#1]
SMP
Mar 16 18:49:27 mordor kernel: [ 5696.670369] last sysfs
file: /sys/devices/platform/it87.552/pwm1_enable
Mar 16 18:49:27 mordor kernel: [ 5696.670421] CPU 2
Mar 16 18:49:27 mordor kernel: [ 5696.670466] Modules linked in: ipt_LOG
xt_tcpudp xt_state xt_mac iptable_filter iptable_nat nf_nat
nf_conntrack_ipv4 nf_defrag_ipv4 iptable_mangle xt_multiport xt_mark
xt_conntrack xt_connmark nf_conntr$
Mar 16 18:49:27 mordor kernel: [ 5696.671003]
Mar 16 18:49:27 mordor kernel: [ 5696.671003] Pid: 21015, comm:
umount.nfs Tainted: P 2.6.38-gentoo #3 Gigabyte Technology
Co., Ltd. GA-790FXTA-UD5/GA-790FXTA-UD5
Mar 16 18:49:27 mordor kernel: [ 5696.671003] RIP:
0010:[<ffffffff810e95c8>] [<ffffffff810e95c8>]
shrink_dcache_for_umount_subtree+0x268/0x270
Mar 16 18:49:27 mordor kernel: [ 5696.671003] RSP: 0018:ffff880219903e08
EFLAGS: 00010296
Mar 16 18:49:27 mordor kernel: [ 5696.671003] RAX: 0000000000000066 RBX:
ffff88015007f300 RCX: 000000000003ffff
Mar 16 18:49:27 mordor kernel: [ 5696.671003] RDX: ffffffff81623888 RSI:
0000000000000046 RDI: ffffffff817509f8
Mar 16 18:49:27 mordor kernel: [ 5696.671003] RBP: ffff88023a1480c0 R08:
000000000001fa7c R09: 0000000000000006
Mar 16 18:49:27 mordor kernel: [ 5696.671003] R10: 0000000000000000 R11:
0000000000000000 R12: ffff88015007f3a0
Mar 16 18:49:27 mordor kernel: [ 5696.671003] R13: ffff88023a14811c R14:
ffff880219903f18 R15: ffff8802107d9640
Mar 16 18:49:27 mordor kernel: [ 5696.671003] FS:
00007ff9ec925700(0000) GS:ffff8800bfa80000(0000) knlGS:0000000000000000
Mar 16 18:49:27 mordor kernel: [ 5696.671003] CS: 0010 DS: 0000 ES:
0000 CR0: 000000008005003b
Mar 16 18:49:27 mordor kernel: [ 5696.671003] CR2: 00007fd326cc2bc8 CR3:
0000000232272000 CR4: 00000000000006e0
Mar 16 18:49:27 mordor kernel: [ 5696.671003] DR0: 0000000000000000 DR1:
0000000000000000 DR2: 0000000000000000
Mar 16 18:49:27 mordor kernel: [ 5696.671003] DR3: 0000000000000000 DR6:
00000000ffff0ff0 DR7: 0000000000000400
Mar 16 18:49:27 mordor kernel: [ 5696.671003] Process umount.nfs (pid:
21015, threadinfo ffff880219902000, task ffff88023ca16780)
Mar 16 18:49:27 mordor kernel: [ 5696.671003] Stack:
Mar 16 18:49:27 mordor kernel: [ 5696.671003] ffff880219af1650
0000000000000000 ffff88023fc07128 ffff880219af1400
Mar 16 18:49:27 mordor kernel: [ 5696.671003] ffff88023a1486c0
ffff880219903f28 ffff88023a03a180 ffffffff810e9624
Mar 16 18:49:27 mordor kernel: [ 5696.671003] ffff88023f4f2480
ffff880219af1400 ffffffff81471460 ffffffff810d5ce5
Mar 16 18:49:27 mordor kernel: [ 5696.671003] Call Trace:
Mar 16 18:49:27 mordor kernel: [ 5696.671003] [<ffffffff810e9624>] ?
shrink_dcache_for_umount+0x54/0x60
Mar 16 18:49:27 mordor kernel: [ 5696.671003] [<ffffffff810d5ce5>] ?
generic_shutdown_super+0x25/0x100
Mar 16 18:49:27 mordor kernel: [ 5696.671003] [<ffffffff810d5e49>] ?
kill_anon_super+0x9/0x40
Mar 16 18:49:27 mordor kernel: [ 5696.671003] [<ffffffff81179acd>] ?
nfs_kill_super+0xd/0x20
Mar 16 18:49:27 mordor kernel: [ 5696.671003] [<ffffffff810d5ee3>] ?
deactivate_locked_super+0x43/0x70
Mar 16 18:49:27 mordor kernel: [ 5696.671003] [<ffffffff810ef4d0>] ?
release_mounts+0x70/0x90
Mar 16 18:49:27 mordor kernel: [ 5696.671003] [<ffffffff810efa44>] ?
sys_umount+0x314/0x3d0
Mar 16 18:49:27 mordor kernel: [ 5696.671003] [<ffffffff8100243b>] ?
system_call_fastpath+0x16/0x1b
Mar 16 18:49:27 mordor kernel: [ 5696.671003] Code: 8b 0a 31 d2 48 85 f6
74 07 48 8b 96 a8 00 00 00 48 05 50 02 00 00 48 89 de 48 c7 c7 e0 7f 52
81 48 89 04 24 31 c0 e8 f1 f0 35 00 <0f> 0b eb fe 0f 0b eb fe 55 53 48
89 fb 48 8d 7f 68 48$
Mar 16 18:49:27 mordor kernel: [ 5696.678048] RIP [<ffffffff810e95c8>]
shrink_dcache_for_umount_subtree+0x268/0x270
Mar 16 18:49:27 mordor kernel: [ 5696.678048] RSP <ffff880219903e08>
Mar 16 18:49:27 mordor kernel: [ 5696.678552] ---[ end trace
24269d237584cd43 ]---
Mar 16 18:49:28 mordor mountd[4362]: Caught signal 15, un-registering
and exiting.
Mar 16 18:49:28 mordor kernel: [ 5697.256066] nfsd: last server has
exited, flushing export cache
Mar 16 18:49:28 mordor kernel: [ 5697.272903] nfsd: last server has
exited, flushing export cache
next prev parent reply other threads:[~2011-03-16 17:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-30882-27@https.bugzilla.kernel.org/>
[not found] ` <201103152102.p2FL2NN8006070@demeter2.kernel.org>
2011-03-15 21:24 ` [Bug 30882] Automatic process group scheduling causes crashes after a while Andrew Morton
2011-03-15 23:54 ` Mehmet Giritli
2011-03-16 2:32 ` Ian Kent
2011-03-16 14:27 ` Mehmet Giritli
2011-03-16 15:21 ` Ian Kent
2011-03-16 15:29 ` Mehmet Giritli
2011-03-16 15:44 ` Ian Kent
2011-03-16 16:48 ` Mehmet Giritli
2011-03-16 17:47 ` Mehmet Giritli [this message]
2011-03-17 2:36 ` Ian Kent
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=1300297634.6144.6.camel@mordor \
--to=mgiritli@giritli.eu \
--cc=akpm@linux-foundation.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=npiggin@kernel.dk \
--cc=raven@themaw.net \
--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 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).