From: chrubis@suse.cz
To: Zeng Linggang <zenglg.jy@cn.fujitsu.com>
Cc: ltp-list <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] [PATCH 2/2] statvfs/statvfs02.c: add new errno testes
Date: Tue, 3 Jun 2014 17:29:20 +0200 [thread overview]
Message-ID: <20140603152920.GA28308@rei> (raw)
In-Reply-To: <1401418662.3225.16.camel@G08JYZSD130126>
Hi!
Both pushed, thanks.
> +static struct test_case_t {
> + char *path;
> + struct statvfs *buf;
> + int exp_errno;
> +} test_cases[] = {
> + {NULL, &buf, EFAULT},
I've changed the testcase, for now, to map PROT_NONE page and set
pointer to it to a path for this testcase because there architectures
that have something mapped on NULL address (itanium if I recall
correctly).
I will deal with this by creating a library function to provide invalid
addresses and fix all the testcases later.
> + {TEST_SYMLINK, &buf, ELOOP},
> + {nametoolong, &buf, ENAMETOOLONG},
> + {"filenoexist", &buf, ENOENT},
> + {"statvfs_file/test", &buf, ENOTDIR},
> +};
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2014-06-03 15:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-30 2:56 [LTP] [PATCH 1/2] statvfs/statvfs01.c: cleanup Zeng Linggang
2014-05-30 2:57 ` [LTP] [PATCH 2/2] statvfs/statvfs02.c: add new errno testes Zeng Linggang
2014-06-03 15:29 ` chrubis [this message]
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=20140603152920.GA28308@rei \
--to=chrubis@suse.cz \
--cc=ltp-list@lists.sourceforge.net \
--cc=zenglg.jy@cn.fujitsu.com \
/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