linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: linux-btrfs@vger.kernel.org
Cc: dhowells@redhat.com, linux-xfs@vger.kernel.org,
	hch@infradead.org, amir73il@gmail.com, david@fromorbit.com,
	fstests@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	Eryu Guan <eguan@redhat.com>
Subject: Does btrfs get nlink on directories wrong? -- was Re: [PATCH 2/4] xfstests: Add first statx test [ver #5]
Date: Wed, 05 Apr 2017 11:53:41 +0100	[thread overview]
Message-ID: <2600.1491389621@warthog.procyon.org.uk> (raw)
In-Reply-To: <20170405103809.GY22845@eguan.usersys.redhat.com>

I've added a test to xfstests that exercises the new statx syscall.  However,
it fails on btrfs:

     Test statx on a directory
    +[!] stx_nlink differs, 1 != 2
    +Failed
    +stat_test failed

because a new directory it creates has an nlink of 1, not 2.  Is this a case
of my making an incorrect assumption or is it an fs bug?

David

       reply	other threads:[~2017-04-05 10:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170405103809.GY22845@eguan.usersys.redhat.com>
     [not found] ` <149132130900.18980.537296385250153410.stgit@warthog.procyon.org.uk>
     [not found]   ` <149132131706.18980.7074156386090748482.stgit@warthog.procyon.org.uk>
2017-04-05 10:53     ` David Howells [this message]
2017-04-05 12:30       ` Does btrfs get nlink on directories wrong? -- was Re: [PATCH 2/4] xfstests: Add first statx test [ver #5] David Sterba
2017-04-05 12:32         ` Amir Goldstein
2017-04-08 15:43           ` Eryu Guan
2017-04-08 21:02           ` David Howells

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=2600.1491389621@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=amir73il@gmail.com \
    --cc=david@fromorbit.com \
    --cc=eguan@redhat.com \
    --cc=fstests@vger.kernel.org \
    --cc=hch@infradead.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    /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).