From: Cyril Hrubis <chrubis@suse.cz>
To: shengyong <shengyong1@huawei.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [RESEND PATCH v3 4/4] syscall/{rename11, renameat01}: do not test EMLINK if subdir limit not availiable
Date: Wed, 28 Jan 2015 11:12:21 +0100 [thread overview]
Message-ID: <20150128101221.GA22007@rei.suse.de> (raw)
In-Reply-To: <54C83795.20809@huawei.com>
Hi!
> > Or is there really reason why we need to differentiate between these two
> > conditions?
> This is also what I'm a little confused. Use different return values, I just
> think we should distinguish different situations. If it returns -1 (or some
> other appropriate values), then we can just skip the test, and this is why
> I passed TPASS to tst_resm() in v2. If it returns 0, which means the fs has
> the limit, but we cannot reach it, something may go wrong (or be changed).
The TCONF flag means "test is not appropriate for current configuration"
which is the case in both cases.
I simply do not see a difference between the case where we know that the
filesystem has no limit and skip the test and the case where we try and
find out that the filesystem has no limit. So I just argue that the
return value for both cases should be 0 because it does not much sense
to distinguish these two in the actuall test.
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2015-01-28 10:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1422323457-184525-1-git-send-email-shengyong1@huawei.com>
[not found] ` <1422323457-184525-2-git-send-email-shengyong1@huawei.com>
2015-01-27 14:40 ` [LTP] [RESEND PATCH v3 1/4] lib: tst_fs_type: add new filesystem types Cyril Hrubis
[not found] ` <1422323457-184525-5-git-send-email-shengyong1@huawei.com>
2015-01-27 14:46 ` [LTP] [RESEND PATCH v3 4/4] syscall/{rename11, renameat01}: do not test EMLINK if subdir limit not availiable Cyril Hrubis
[not found] ` <54C83795.20809@huawei.com>
2015-01-28 10:12 ` Cyril Hrubis [this message]
[not found] ` <1422323457-184525-4-git-send-email-shengyong1@huawei.com>
2015-01-27 14:48 ` [LTP] [RESEND PATCH v3 3/4] lib/tests: do not print max dir number " Cyril Hrubis
[not found] ` <1422323457-184525-3-git-send-email-shengyong1@huawei.com>
2015-01-27 15:00 ` [LTP] [RESEND PATCH v3 2/4] lib/tst_fs_link_count.c: check fs type and do not fill subdir if no limit Cyril Hrubis
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=20150128101221.GA22007@rei.suse.de \
--to=chrubis@suse.cz \
--cc=ltp-list@lists.sourceforge.net \
--cc=shengyong1@huawei.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