Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755288AbbHQMhL (ORCPT ); Mon, 17 Aug 2015 08:37:11 -0400 Received: from mx.gnuher.de ([144.76.235.56]:54355 "EHLO mx.gnuher.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754671AbbHQMhJ (ORCPT ); Mon, 17 Aug 2015 08:37:09 -0400 Date: Mon, 17 Aug 2015 14:37:04 +0200 From: Sven Geggus To: "Eric W. Biederman" Cc: linux-kernel@vger.kernel.org, trond.myklebust@primarydata.com, linux-nfs@vger.kernel.org Subject: Re: nfs-root: destructive call to __detach_mounts /dev Message-ID: <20150817123703.GA25546@geggus.net> References: <20150731114230.GA31037@geggus.net> <87r3noieqg.fsf@x220.int.ebiederm.org> <20150814110140.GA25799@geggus.net> <87lhddhpso.fsf@x220.int.ebiederm.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <87lhddhpso.fsf@x220.int.ebiederm.org> X-MimeOLE: Produced By Exchange Microsoft V6.6.6 User-Agent: Mutt/1.5.21 (2010-09-15) X-remote-host: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2617 Lines: 46 Eric W. Biederman wrote: > I don't have a clue what the issue would be but I would start with > something like the patch below. OK using it I got the following... This time with /dev on another machine (same nfs root-fs): Aug 17 13:57:04 dhcp195 kernel: NFS: nfs_lookup_revalidate(/dev): nfs_lookup_verify_inode() failed Aug 17 13:57:04 dhcp195 kernel: NFS: nfs_lookup_revalidate(/dev) is invalid Aug 17 13:57:04 dhcp195 kernel: NFSROOT __detach_mounts: dev Aug 17 13:57:04 dhcp195 kernel: CPU: 3 PID: 32644 Comm: modtrack Tainted: P O 4.1.6-lomac1-00296-gfeae456 #7 Aug 17 13:57:04 dhcp195 kernel: Hardware name: System manufacturer System Product Name/P7P55D, BIOS 1807 07/22/2010 Aug 17 13:57:04 dhcp195 kernel: ffff88021315bc18 ffff88021315bbd8 ffffffff81560638 000000000000b413 Aug 17 13:57:04 dhcp195 kernel: ffff880216460f18 ffff88021315bbf8 ffffffff81106e1f 000000000000001b Aug 17 13:57:04 dhcp195 kernel: ffff880216460f18 ffff88021315bc48 ffffffff810ffcf5 0000000005dd05dd Aug 17 13:57:04 dhcp195 kernel: Call Trace: Aug 17 13:57:04 dhcp195 kernel: [] dump_stack+0x4c/0x6e Aug 17 13:57:04 dhcp195 kernel: [] __detach_mounts+0x20/0xdf Aug 17 13:57:04 dhcp195 kernel: [] d_invalidate+0x9a/0xc8 Aug 17 13:57:04 dhcp195 kernel: [] lookup_fast+0x1f5/0x26f Aug 17 13:57:04 dhcp195 kernel: [] do_last.isra.43+0xd6/0x9fb Aug 17 13:57:04 dhcp195 kernel: [] path_openat+0x1d1/0x53e Aug 17 13:57:04 dhcp195 kernel: [] ? user_path_at_empty+0x63/0x93 Aug 17 13:57:04 dhcp195 kernel: [] do_filp_open+0x35/0x85 Aug 17 13:57:04 dhcp195 kernel: [] ? find_next_zero_bit+0x17/0x1d Aug 17 13:57:04 dhcp195 kernel: [] ? __alloc_fd+0xdd/0xef Aug 17 13:57:04 dhcp195 kernel: [] do_sys_open+0x146/0x1d5 Aug 17 13:57:04 dhcp195 kernel: [] SyS_openat+0xf/0x11 Aug 17 13:57:04 dhcp195 kernel: [] system_call_fastpath+0x12/0x6a So this looks like I would need to add some debug output to "nfs_lookup_verify_inode" then right? Sven -- Why are there so many Unix-haters-handbooks and not even one Microsoft-Windows-haters handbook? Gurer vf ab arrq sbe n unaqobbx gb ungr Zvpebfbsg Jvaqbjf! /me is giggls@ircnet, http://sven.gegg.us/ on the Web -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/