From: Cyril Hrubis <chrubis@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v5] Refactor fork05 using new LTP API
Date: Tue, 10 Sep 2024 15:15:42 +0200 [thread overview]
Message-ID: <ZuBGfgODoO6-NZD4@yuki.lan> (raw)
In-Reply-To: <20240830132905.14902-1-andrea.cervesato@suse.de>
Hi!
> +/*\
> + * [Description]
> *
> - * http://www.sgi.com$
> + * This test verifies that LDT is propagated correctly from parent process to
> + * the child process.
> *
> - * For further information regarding this notice, see:$
> + * On Friday, May 2, 2003 at 09:47:00AM MST, Ulrich Drepper wrote:
> + * Robert Williamson wrote:
> *
> - * http://oss.sgi.com/projects/GenInfo/NoticeExplan/
> + * I'm getting a SIGSEGV with one of our tests, fork05.c, that apparently
> + * you wrote (attached below). The test passes on my 2.5.68 machine running
> + * SuSE 8.0 (glibc 2.2.5 and Linuxthreads), however it segmentation faults on
> + * RedHat 9 running 2.5.68. The test seems to "break" when it attempts to run
> + * the assembly code....could you take a look at it?
> *
> + * There is no need to look at it, I know it cannot work anymore on recent
> + * systems. Either change all uses of %gs to %fs or skip the entire patch
> + * if %gs has a nonzero value.
> *
> - * Linux Test Project - Silicon Graphics, Inc.
> - * TEST IDENTIFIER : fork05
> - * EXECUTED BY : anyone
> - * TEST TITLE : Make sure LDT is propagated correctly
> - * TEST CASE TOTAL : 1
> - * CPU TYPES : i386
> - * AUTHORS : Ulrich Drepper
> - * Nate Straz
> + * On Sat, Aug 12, 2000 at 12:47:31PM -0700, Ulrich Drepper wrote:
You need an empty line here in order for the next block to render
correctly. Have you checked the metadata.html?
> + * Ever since the %gs handling was fixed in the 2.3.99 series the
> + * appended test program worked. Now with 2.4.0-test6 it's not working
> + * again. Looking briefly over the patch from test5 to test6 I haven't
> + * seen an immediate candidate for the breakage. It could be missing
> + * propagation of the LDT to the new process (and therefore an invalid
> + * segment descriptor) or simply clearing %gs.
> *
...
> + if (WIFSIGNALED(status))
> + tst_res(TFAIL, "Child crashed with %s", tst_strsig(WTERMSIG(status)));
I suppose we should fail the test unless the child returned with 0. I.e.
if (WIFEXITTED(status) && WEXITSTATUS(status))
tst_res(TPASS, "Child did exit with 0");
else
tst_res(TFAIL, "Child %s", tst_strstatus(status));
Other than these two minor things:
Reviewed-by: Cyril Hrubis <chrubis@suse.cz>
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2024-09-10 13:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 13:29 [LTP] [PATCH v5] Refactor fork05 using new LTP API Andrea Cervesato
2024-09-10 13:15 ` Cyril Hrubis [this message]
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=ZuBGfgODoO6-NZD4@yuki.lan \
--to=chrubis@suse.cz \
--cc=andrea.cervesato@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox