Re: odd sysfs find behavior, was: Re: [PATCH v6 00/10] Implement NVMe Namespace Descriptor Identification

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,

On Sun, Jun 18, 2017 at 03:43:36PM +0200, Christoph Hellwig wrote:
> 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

So, looks like this is the debugfs automount mechanism changing nlinks
across automounts and confusing find in the process.  Greg?

Thanks.

-- 
tejun



[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux