Return-Path: linux-nfs-owner@vger.kernel.org Received: from mail-ve0-f174.google.com ([209.85.128.174]:46305 "EHLO mail-ve0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751877Ab3IGUvJ convert rfc822-to-8bit (ORCPT ); Sat, 7 Sep 2013 16:51:09 -0400 MIME-Version: 1.0 In-Reply-To: <522B9010.8070902@gmx.de> References: <52075E01.7030506@gmx.de> <20130812143640.GF4596@quack.suse.cz> <20130813215313.GH17781@fieldses.org> <20130827180655.GE14809@fieldses.org> <521E318C.7040401@gmx.de> <522B9010.8070902@gmx.de> Date: Sat, 7 Sep 2013 22:51:07 +0200 Message-ID: Subject: Re: [uml-devel] Issues with a rather unusual configured NFS server From: richard -rw- weinberger To: =?ISO-8859-1?Q?Toralf_F=F6rster?= Cc: "J. Bruce Fields" , Linux NFS mailing list , "J. Bruce Fields" , "user-mode-linux-devel@lists.sourceforge.net" , Linux Kernel , Jan Kara , linux-ext4@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-nfs-owner@vger.kernel.org List-ID: On Sat, Sep 7, 2013 at 10:44 PM, Toralf F?rster 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 , unused1=0, unused2=0x85e76e0 ) at arch/um/kernel/um_arch.c:240 > #5 0x0809a398 in notifier_call_chain (nl=0x0, val=0, v=0x85e76e0 , nr_to_call=-2, nr_calls=0x0) at kernel/notifier.c:93 > #6 0x0809a4e3 in __atomic_notifier_call_chain (nr_calls=, nr_to_call=, v=, val=, nh=) at kernel/notifier.c:182 > #7 atomic_notifier_call_chain (nh=0x85e76c4 , val=0, v=0x85e76e0 ) 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