All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] syscall/fcntl33.c: fix test on FUSE fs
Date: Tue, 19 Apr 2016 20:01:52 +0200	[thread overview]
Message-ID: <20160419180151.GE21282@rei.lan> (raw)
In-Reply-To: <1461086247-23235-1-git-send-email-alexey.kodanev@oracle.com>

Hi!
> Even though a child process is waiting for a parent to be in 'S'
> state before triggering SIGIO, the signal might come earlier than
> sigtimedwait() being invoked in the parent process. As a result the
> parent waited for the event that had already happened.
> 
> I can only think about that the parent process may be in a sleep state
> somehow while executing open() syscall on which it might sleep while
> running it on FUSE FS:
> vfs -> fuse kernel driver -> userspace implementation.

That sounds plausible to me. Depending on the actuall FUSE filesystem it
may do basically anything.

> It can be fixed if we move open() before fork.
> 
> Signed-off-by: Alexey Kodanev <alexey.kodanev@oracle.com>
> ---
>  testcases/kernel/syscalls/fcntl/fcntl33.c |   11 ++++++-----
>  1 files changed, 6 insertions(+), 5 deletions(-)
> 
> diff --git a/testcases/kernel/syscalls/fcntl/fcntl33.c b/testcases/kernel/syscalls/fcntl/fcntl33.c
> index 2d69866..13616c6 100644
> --- a/testcases/kernel/syscalls/fcntl/fcntl33.c
> +++ b/testcases/kernel/syscalls/fcntl/fcntl33.c
> @@ -146,16 +146,17 @@ static void setup(void)
>  
>  static void do_test(int i)
>  {
> -	pid_t cpid;
> +	fd = SAFE_OPEN(cleanup, "file", O_RDONLY);
> +
> +	pid_t cpid = tst_fork();
>  
> -	cpid = tst_fork();
>  	if (cpid < 0)
>  		tst_brkm(TBROK | TERRNO, cleanup, "fork() failed");
>  
> -	if (cpid == 0)
> +	if (cpid == 0) {
> +		SAFE_CLOSE(NULL, fd);
>  		do_child(i);
> -
> -	fd = SAFE_OPEN(cleanup, "file", O_RDONLY);
> +	}

Looks good.

Another possible solution would be to use checkpoints and wait in the
child before we call tst_process_state_wait() and wake it up from parent
just before we call the fcntl(). But that would be more complicated than
this.

-- 
Cyril Hrubis
chrubis@suse.cz

  reply	other threads:[~2016-04-19 18:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-19 17:17 [LTP] [PATCH] syscall/fcntl33.c: fix test on FUSE fs Alexey Kodanev
2016-04-19 18:01 ` Cyril Hrubis [this message]
2016-04-20 10:55   ` Alexey Kodanev

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=20160419180151.GE21282@rei.lan \
    --to=chrubis@suse.cz \
    --cc=ltp@lists.linux.it \
    /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.