From: richard -rw- weinberger <richard.weinberger@gmail.com>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
Linux NFS mailing list <linux-nfs@vger.kernel.org>,
"J. Bruce Fields" <bfields@redhat.com>,
"user-mode-linux-devel@lists.sourceforge.net"
<user-mode-linux-devel@lists.sourceforge.net>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Jan Kara <jack@suse.cz>,
linux-ext4@vger.kernel.org
Subject: Re: [uml-devel] Issues with a rather unusual configured NFS server
Date: Sat, 7 Sep 2013 22:51:07 +0200 [thread overview]
Message-ID: <CAFLxGvzGLYYmrHHZ+cLehp5x9gt3MFOMzgF26C-=PxtSoXhWTg@mail.gmail.com> (raw)
In-Reply-To: <522B9010.8070902@gmx.de>
On Sat, Sep 7, 2013 at 10:44 PM, Toralf Förster <toralf.foerster@gmx.de> wrote:
> Today I run latest git tree with a patched UML (this patch + one for xterm issues) and got 2 times a core dump
> when I fuzzy test an UML machine with a nearly identical scenario as already described but just shutdowned
> both UML images instead of shooting one of it in the head.
>
> I'll probably need time to figure out a test case, but just as a pre-info here's the back trace:
>
> tfoerste@n22 ~ $ gdb --core=/mnt/ramdisk/core /usr/local/bin/linux-v3.11-7550-g768c9d3 -n -batch -ex bt
>
> warning: core file may not match specified executable file.
> [New LWP 7470]
> [New LWP 7479]
> [New LWP 7477]
> [New LWP 7478]
> Core was generated by `/usr/local/bin/linux-v3.11-7550-g768c9d3 earlyprintk ubda=/home/tfoerste/virtua'.
> Program terminated with signal 6, Aborted.
> #0 0xb77be424 in __kernel_vsyscall ()
> #0 0xb77be424 in __kernel_vsyscall ()
> #1 0x083aada5 in kill ()
> #2 0x0807163d in uml_abort () at arch/um/os-Linux/util.c:93
> #3 0x08071925 in os_dump_core () at arch/um/os-Linux/util.c:138
> #4 0x080613a7 in panic_exit (self=0x85b1518 <panic_exit_notifier>, unused1=0, unused2=0x85e76e0 <buf.15920>) at arch/um/kernel/um_arch.c:240
> #5 0x0809a398 in notifier_call_chain (nl=0x0, val=0, v=0x85e76e0 <buf.15920>, nr_to_call=-2, nr_calls=0x0) at kernel/notifier.c:93
> #6 0x0809a4e3 in __atomic_notifier_call_chain (nr_calls=<optimized out>, nr_to_call=<optimized out>, v=<optimized out>, val=<optimized out>, nh=<optimized out>) at kernel/notifier.c:182
> #7 atomic_notifier_call_chain (nh=0x85e76c4 <panic_notifier_list>, val=0, v=0x85e76e0 <buf.15920>) at kernel/notifier.c:191
> #8 0x08408628 in panic (fmt=0x0) at kernel/panic.c:128
> #9 0x081131c9 in shrink_dcache_for_umount_subtree (dentry=0x428028f0) at fs/dcache.c:941
That is:
if (dentry->d_lockref.count != 0) {
printk(KERN_ERR
"BUG: Dentry %p{i=%lx,n=%s}"
" still in use (%d)"
" [unmount of %s %s]\n",
dentry,
dentry->d_inode ?
dentry->d_inode->i_ino : 0UL,
dentry->d_name.name,
dentry->d_lockref.count,
dentry->d_sb->s_type->name,
dentry->d_sb->s_id);
BUG();
}
Do you also have the console output?
--
Thanks,
//richard
next prev parent reply other threads:[~2013-09-07 20:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-11 9:48 Issues with a rather unusual configured NFS server Toralf Förster
2013-08-12 14:36 ` Jan Kara
2013-08-13 21:53 ` J. Bruce Fields
2013-08-14 16:44 ` Toralf Förster
2013-08-27 18:06 ` J. Bruce Fields
2013-08-28 17:21 ` Toralf Förster
2013-08-29 9:57 ` [uml-devel] " richard -rw- weinberger
2013-08-29 13:30 ` J. Bruce Fields
2013-08-30 14:10 ` Toralf Förster
2013-08-30 14:25 ` J. Bruce Fields
2013-08-30 14:36 ` Richard Weinberger
2013-08-30 18:27 ` Michael Richardson
2013-09-07 20:44 ` Toralf Förster
2013-09-07 20:51 ` richard -rw- weinberger [this message]
2013-09-10 14:09 ` J. Bruce Fields
2013-09-10 15:51 ` Toralf Förster
2013-09-22 16:58 ` Toralf Förster
2013-09-23 17:41 ` J. Bruce Fields
2013-10-02 20:29 ` Toralf Förster
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='CAFLxGvzGLYYmrHHZ+cLehp5x9gt3MFOMzgF26C-=PxtSoXhWTg@mail.gmail.com' \
--to=richard.weinberger@gmail.com \
--cc=bfields@fieldses.org \
--cc=bfields@redhat.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=toralf.foerster@gmx.de \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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).