From: Christoph Hellwig <hch@infradead.org>
To: David Howells <dhowells@redhat.com>
Cc: linux-xfs@vger.kernel.org, hch@infradead.org, amir73il@gmail.com,
david@fromorbit.com, fstests@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 1/2] xfstests: Add first statx test
Date: Fri, 31 Mar 2017 09:27:23 -0700 [thread overview]
Message-ID: <20170331162723.GA1693@infradead.org> (raw)
In-Reply-To: <149097291264.20089.7010494679305716312.stgit@warthog.procyon.org.uk>
This only compiles with warnings for me:
stat_test.c: In function 'main':
stat_test.c:557:3: warning: 'sval' may be used uninitialized in this function [-Wmaybe-uninitialized]
check(sval == scheck,
^
stat_test.c:451:20: note: 'sval' was declared here
long long scheck, sval;
^
stat_test.c:542:3: warning: 'uval' may be used uninitialized in this function [-Wmaybe-uninitialized]
check(uval == ucheck,
^
stat_test.c:450:29: note: 'uval' was declared here
unsigned long long ucheck, uval;
^
And running it then fails for me on Debian stable:
--- tests/generic/420.out 2017-03-31 16:24:11.643845876 +0000
+++ /root/xfstests/results//generic/420.out.bad 2017-03-31 16:26:23.820512545 +0000
@@ -8,4 +8,10 @@
20+0 records out
Test statx on a symlink
Test statx on an AF_UNIX socket
+nc: invalid option -- 'U'
+/bin/nc: invalid option -- 'U'
+nc -h for helpnc -h for help
+
+/mnt/test/420-sock: No such file or directory
Test a hard link to a file
+/mnt/test/420-sock: No such file or directory
next prev parent reply other threads:[~2017-03-31 16:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-31 15:08 [PATCH 1/2] xfstests: Add first statx test David Howells
2017-03-31 15:08 ` [PATCH 2/2] xfstests: Partially expand the documentation David Howells
2017-03-31 16:27 ` Christoph Hellwig
2017-03-31 16:27 ` Christoph Hellwig [this message]
2017-03-31 16:48 ` [PATCH 1/2] xfstests: Add first statx test David Howells
2017-03-31 17:19 ` Christoph Hellwig
2017-03-31 17:24 ` David Howells
2017-04-01 7:35 ` Eryu Guan
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=20170331162723.GA1693@infradead.org \
--to=hch@infradead.org \
--cc=amir73il@gmail.com \
--cc=david@fromorbit.com \
--cc=dhowells@redhat.com \
--cc=fstests@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.