From: chrubis@suse.cz
To: "gux.fnst" <gux.fnst@cn.fujitsu.com>
Cc: ltp-list <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] [PATCH 2/2] rmdir/rmdir02.c: add ELOOP, EROFS and EBUSY error value tests
Date: Mon, 19 May 2014 14:15:53 +0200 [thread overview]
Message-ID: <20140519121553.GA4334@rei> (raw)
In-Reply-To: <53756E7A.6070009@cn.fujitsu.com>
Hi!
> > I've removed the EUID changes for all because these has no effect on the
> > test behavior (at least I haven't figured out why they are needed).
>
> I tested with the UEID is aimed to prove the system call can be executed
> right with a normal user account, to provide a more overall testcase.
I've looked at the testcase again, and it seems to me that there would
be no difference on the results of these testcases (IMHO they would
still hit the same check in the rmdir() syscall in kernel both under
privileged and unprivileged user). Did I miss somethink?
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2014-05-19 12:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-17 10:50 [LTP] [PATCH 1/2] rmdir/rmdir02.c: cleanup gux.fnst
2014-04-17 10:50 ` [LTP] [PATCH 2/2] rmdir/rmdir02.c: add ELOOP, EROFS and EBUSY error value tests gux.fnst
2014-05-15 12:14 ` chrubis
[not found] ` <53756E7A.6070009@cn.fujitsu.com>
2014-05-19 12:15 ` chrubis [this message]
2014-05-15 12:12 ` [LTP] [PATCH 1/2] rmdir/rmdir02.c: cleanup chrubis
2014-05-15 12:15 ` chrubis
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=20140519121553.GA4334@rei \
--to=chrubis@suse.cz \
--cc=gux.fnst@cn.fujitsu.com \
--cc=ltp-list@lists.sourceforge.net \
/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