public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Jan Stancek <jstancek@redhat.com>
To: Xiaoguang Wang <wangxg.fnst@cn.fujitsu.com>
Cc: ltp-list@lists.sourceforge.net, Artem Savkov <asavkov@redhat.com>
Subject: Re: [LTP] [PATCH 2/2] syscalls/getcwd04.c: regression test for getcwd(2)
Date: Mon, 21 Jul 2014 05:04:27 -0400 (EDT)	[thread overview]
Message-ID: <38788431.12648558.1405933467675.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1405419229-4222-2-git-send-email-wangxg.fnst@cn.fujitsu.com>




----- Original Message -----
> From: "Xiaoguang Wang" <wangxg.fnst@cn.fujitsu.com>
> To: ltp-list@lists.sourceforge.net
> Sent: Tuesday, 15 July, 2014 12:13:49 PM
> Subject: [LTP] [PATCH 2/2] syscalls/getcwd04.c: regression test for getcwd(2)
> 
> Note: this test has already been in xfstests generic/028 test case,
> I just port it to LTP.
> 
> Kernel commit '232d2d60aa5469bb097f55728f65146bd49c1d25' introduced a race
> condition that causes getcwd(2) to return "/" instead of correct path.
>     232d2d6 dcache: Translating dentry into pathname without
>             taking rename_lock
> 
> And these two kernel commits have fixed this bug:
>   ede4cebce16f5643c61aedd6d88d9070a1d23a68
>      prepend_path() needs to reinitialize dentry/vfsmount/mnt on restarts
>   f6500801522c61782d4990fa1ad96154cb397cd4
>      f650080 __dentry_path() fixes
> 
> This test is to check whether this bug exists in the running kernel,
> or whether this bug has been fixed.
> 
> Signed-off-by: Xiaoguang Wang <wangxg.fnst@cn.fujitsu.com>

Hi,

looks good to me.

> I have run this test case in RHEL7.0GA, Fedora19, v3.11-7758-g232d2d6 and 3.16.0-rc4+.
> RHEL7.0GA has this kernel bug, so this test case fails.

I can confirm this, with note that I've seen it happen only on systems with 2+ CPUs.

> + *
> + */
> +
> +#include <stdio.h>
> +#include <errno.h>
> +#include <fcntl.h>
> +#include <sys/types.h>
> +#include <unistd.h>
> +
> +#include "usctest.h"
> +#include "test.h"
> +#include "safe_macros.h"
> +
> +#define TIMEOUT	5
> +
> +static void setup(void);
> +static void cleanup(void);
> +static void do_child(void);
> +static void sigproc(int sig);
> +static volatile sig_atomic_t end;
> +static char init_cwd[PATH_MAX];
> +
> +char *TCID = "getcwd04";
> +int TST_TOTAL = 1;
> +
> +int main(int ac, char **av)
> +{
> +	int status;
> +	const char *msg;
> +	char cur_cwd[PATH_MAX];
> +	pid_t child;
> +
> +	msg = parse_opts(ac, av, NULL, NULL);
> +	if (msg != NULL)
> +		tst_brkm(TBROK, NULL, "OPTION PARSING ERROR - %s", msg);
> +
> +	setup();
> +
> +	child = tst_fork();
> +	if (child < 0)
> +		tst_brkm(TBROK | TERRNO, cleanup, "fork failed");
> +
> +	if (child == 0)
> +		do_child();
> +
> +	 while (1) {
> +		SAFE_GETCWD(cleanup, cur_cwd, PATH_MAX);
> +		if (strncmp(init_cwd, cur_cwd, PATH_MAX)) {
> +			tst_resm(TFAIL, "initial current work directory is "
> +				 "%s, now is %s. Bug is reproduced!",
> +				 init_cwd, cur_cwd);
> +			break;
> +		}
> +
> +		if (end) {
> +			tst_resm(TPASS, "Bug is not reproduced!");
> +			break;
> +		}
> +	}
> +
> +	SAFE_KILL(cleanup, child, SIGKILL);
> +	SAFE_WAITPID(cleanup, child, &status, 0);
> +
> +	cleanup();
> +	tst_exit();
> +}
> +
> +static void setup(void)
> +{
> +	tst_sig(FORK, DEF_HANDLER, cleanup);
> +
> +	TEST_PAUSE;
> +
> +	tst_tmpdir();
> +
> +	if (signal(SIGALRM, sigproc) == SIG_ERR)
> +		tst_brkm(TBROK | TERRNO, cleanup, "signal(SIGALRM) failed");
> +
> +	alarm(TIMEOUT);
> +
> +	SAFE_MKDIR(cleanup, "testdir", 0755);
> +	SAFE_CHDIR(cleanup, "testdir");

Is this extra dir needed? tst_tmpdir will already make one.

Regards,
Jan

> +
> +	SAFE_GETCWD(cleanup, init_cwd, PATH_MAX);
> +}
> +
> +static void sigproc(int sig)
> +{
> +	end = sig;
> +}
> +
> +static void do_child(void)
> +{
> +	unsigned int i = 0;
> +	char c_name[PATH_MAX] = "testfile", n_name[PATH_MAX];
> +
> +	SAFE_TOUCH(NULL, c_name, 0644, NULL);
> +
> +	while (1) {
> +		snprintf(n_name, PATH_MAX, "testfile%u", i++);
> +		SAFE_RENAME(NULL, c_name, n_name);
> +		strncpy(c_name, n_name, PATH_MAX);
> +	}
> +}
> +
> +static void cleanup(void)
> +{
> +	TEST_CLEANUP;
> +
> +	tst_rmdir();
> +}
> --
> 1.8.2.1
> 
> 
> ------------------------------------------------------------------------------
> Want fast and easy access to all the code in your enterprise? Index and
> search up to 200,000 lines of code with a free copy of Black Duck
> Code Sight - the same software that powers the world's largest code
> search on Ohloh, the Black Duck Open Hub! Try it now.
> http://p.sf.net/sfu/bds
> _______________________________________________
> Ltp-list mailing list
> Ltp-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ltp-list
> 

------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  parent reply	other threads:[~2014-07-21  9:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-15 10:13 [LTP] [PATCH 1/2] lib: add SAFE_RENAME() Xiaoguang Wang
2014-07-15 10:13 ` [LTP] [PATCH 2/2] syscalls/getcwd04.c: regression test for getcwd(2) Xiaoguang Wang
2014-07-15 10:21   ` Xiaoguang Wang
2014-07-21  9:04   ` Jan Stancek [this message]
2014-07-21  9:09     ` Wanlong Gao
2014-07-21  9:23       ` Xiaoguang Wang
2014-07-27  8:42         ` Xiaoguang Wang
2014-07-27  9:00           ` [LTP] [PATCH v2 1/2] lib: add SAFE_RENAME() Xiaoguang Wang
2014-07-27  9:00             ` [LTP] [PATCH v2 2/2] syscalls/getcwd04.c: regression test for getcwd(2) Xiaoguang Wang
2014-08-01  1:51             ` [LTP] [PATCH v2 1/2] lib: add SAFE_RENAME() Wanlong Gao
2014-07-21  9:33       ` [LTP] [PATCH 2/2] syscalls/getcwd04.c: regression test for getcwd(2) Jan Stancek
2014-07-21  9:40         ` Wanlong Gao
2014-07-21  9:58           ` Jan Stancek

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=38788431.12648558.1405933467675.JavaMail.zimbra@redhat.com \
    --to=jstancek@redhat.com \
    --cc=asavkov@redhat.com \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=wangxg.fnst@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