From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from verein.lst.de ([213.95.11.211]:52113 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752925AbdFRNni (ORCPT ); Sun, 18 Jun 2017 09:43:38 -0400 Date: Sun, 18 Jun 2017 15:43:36 +0200 From: Christoph Hellwig To: Tejun Heo Cc: Christoph Hellwig , Greg Kroah-Hartman , Linus Torvalds , linux-fsdevel@vger.kernel.org Subject: Re: odd sysfs find behavior, was: Re: [PATCH v6 00/10] Implement NVMe Namespace Descriptor Identification Message-ID: <20170618134336.GA32701@lst.de> References: <20170616094056.GA12465@lst.de> <905ed2e6-1c1c-f3a3-5391-66e42fb61861@suse.de> <20170616095837.GA14217@lst.de> <20170617120814.GA13236@lst.de> <20170618011250.GA1987@kroah.com> <20170618073249.GA25797@lst.de> <20170618073305.GB25797@lst.de> <20170618102020.GA28042@htj.duckdns.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170618102020.GA28042@htj.duckdns.org> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Sun, Jun 18, 2017 at 06:20:20AM -0400, Tejun Heo wrote: > If you "cd /sys/kernel/debug/tracing; cd -" before doing the find, > does it succeed the first time? It could be that the on-demand > mounting of tracefs is giving incoherent results across the mounting > and confusing find. Yes, that works fine: root@testvm:~# cd /sys/kernel/debug/tracing; cd - /root root@testvm:~# find /sys -name uuid /sys/devices/virtual/nvme-fabrics/ctl/nvme3/nvme3n1/uuid /sys/devices/virtual/nvme-fabrics/ctl/nvme2/nvme2n1/uuid