All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xiao Yang <yangx.jy@cn.fujitsu.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] sigwaitinfo01: recent glibc calls syscall directly
Date: Mon, 15 Oct 2018 15:17:20 +0800	[thread overview]
Message-ID: <5BC43F00.3080109@cn.fujitsu.com> (raw)
In-Reply-To: <dbe33b2d18cd674954668fa62ab61f0d57e0c704.1536739517.git.jstancek@redhat.com>

On 2018/09/12 16:09, Jan Stancek wrote:
> glibc commit
>    8b0e795aaa44 ("Simplify Linux sig{timed}wait{info} implementations")
> changed sigwaitinfo to call sigtimedwait, which calls rt_sigtimedwait
> syscall directly.
>
> So, an invalid pointer no longer crashes child process and test
> reports failure. Fix it by accepting either crash or EFAULT.
>
> Signed-off-by: Jan Stancek<jstancek@redhat.com>
> ---
>   .../kernel/syscalls/sigwaitinfo/sigwaitinfo01.c    | 29 +++++++++++++++++++---
>   1 file changed, 25 insertions(+), 4 deletions(-)
>
> diff --git a/testcases/kernel/syscalls/sigwaitinfo/sigwaitinfo01.c b/testcases/kernel/syscalls/sigwaitinfo/sigwaitinfo01.c
> index 95a9436a44c9..02730364db4d 100644
> --- a/testcases/kernel/syscalls/sigwaitinfo/sigwaitinfo01.c
> +++ b/testcases/kernel/syscalls/sigwaitinfo/sigwaitinfo01.c
> @@ -371,19 +371,40 @@ void test_bad_address2(swi_func sigwaitinfo, int signo)
>   		tst_brkm(TBROK | TERRNO, NULL, "fork() failed");
>   	case 0:
>   		signal(SIGSEGV, SIG_DFL);
> +
> +		/*
> +		 * depending on glibc implementation we should
> +		 * either crash or get EFAULT
> +		 */
>   		TEST(sigwaitinfo((void *)1, NULL, NULL));
>
> -		_exit(0);
> +		if (TEST_RETURN == -1&&  TEST_ERRNO == EFAULT)
> +			_exit(0);
> +
> +		tst_resm(TINFO, "swi_func returned: %ld, errno: %d",
> +			TEST_RETURN, TEST_ERRNO);
Hi Jan,

Perhaps, just use tst_resm(TINFO | TTERRNO, "swi_func returned: %ld", TEST_RETURN);

Other than that this patch looks good to me, and it works well on glibc v2.28.

Thanks,
Xiao Yang

> +		_exit(1);
>   		break;
>   	default:
>   		break;
>   	}
>
>   	SUCCEED_OR_DIE(waitpid, "waitpid failed", pid,&status, 0);
> -	if (WIFSIGNALED(status)&&  WTERMSIG(status) == SIGSEGV)
> +
> +	if ((WIFSIGNALED(status)&&  WTERMSIG(status) == SIGSEGV)
> +		|| (WIFEXITED(status)&&  WEXITSTATUS(status) == 0)) {
>   		tst_resm(TPASS, "Test passed");
> -	else
> -		tst_resm(TFAIL, "Unrecognised child exit code");
> +		return;
> +	}
> +
> +	if (WIFEXITED(status)) {
> +		tst_resm(TFAIL, "Unrecognised child exit code: %d",
> +			WEXITSTATUS(status));
> +	}
> +	if (WIFSIGNALED(status)) {
> +		tst_resm(TFAIL, "Unrecognised child termsig: %d",
> +			WTERMSIG(status));
> +	}
>   }
>
>   void test_bad_address3(swi_func sigwaitinfo, int signo)




  reply	other threads:[~2018-10-15  7:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-12  8:09 [LTP] [PATCH] sigwaitinfo01: recent glibc calls syscall directly Jan Stancek
2018-10-15  7:17 ` Xiao Yang [this message]
2018-10-15  7:34   ` 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=5BC43F00.3080109@cn.fujitsu.com \
    --to=yangx.jy@cn.fujitsu.com \
    --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.