From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 2/4] syscalls/modify_ldt: Replace TINFO with TPASS or TFAIL
Date: Thu, 6 May 2021 14:06:29 +0200 [thread overview]
Message-ID: <YJPbxQikXPap5DHW@pevik> (raw)
In-Reply-To: <YJPNgGwlZBLMaJOd@yuki>
Hi,
> Hi!
> > FYI: since merging this patch (f5e8e6b11) test fails on this. Is it expected?
> > I haven't looked closer whether it's a test bug or real issue.
> What is the test failure output? The only part that was change that
$ ./modify_ldt02
modify_ldt02 1 TPASS : value read as expected
modify_ldt02 0 TINFO : received signal: 11
modify_ldt02 2 TFAIL : modify_ldt02.c:136: Did not generate SEGV
(I wrote my report below affected line)
11 is SIGSEGV, thus there must be a bug in a test, which probably has been there
before (test just didn't check). It's strange that WTERMSIG(status) returns 0
instead of 11.
> could introduce difference in the output is as far as I can tell this:
> /*
> * Create a new LDT segment.
> */
> if (create_segment(seg, sizeof(seg)) == -1) {
> - tst_brkm(TINFO, cleanup, "Creation of segment failed");
> + tst_brkm(TBROK, cleanup, "Creation of segment failed");
> }
> Which would mean that the test was broken before the change but just
> haven't produced any errors.
Yes.
Old results:
modify_ldt02 0 TINFO : Enter block 1
modify_ldt02 0 TINFO : block 1 PASSED
modify_ldt02 0 TINFO : Exit block 1
modify_ldt02 0 TINFO : Enter block 2
modify_ldt02 0 TINFO : received signal: 11
modify_ldt02 0 TINFO : block 2 PASSED
NOTE: no PASS/FAIL.
Kind regards,
Petr
next prev parent reply other threads:[~2021-05-06 12:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 12:52 [LTP] [PATCH 2/4] syscalls/modify_ldt: Replace TINFO with TPASS or TFAIL Zhao Gongyi
2021-04-30 13:24 ` Cyril Hrubis
2021-05-06 10:44 ` Petr Vorel
2021-05-06 11:05 ` Cyril Hrubis
2021-05-06 12:06 ` Petr Vorel [this message]
2021-05-06 11:47 ` Cyril Hrubis
-- strict thread matches above, loose matches on Subject: below --
2021-05-06 11:15 zhaogongyi
2021-05-06 11:23 zhaogongyi
2021-05-06 11:57 ` Petr Vorel
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=YJPbxQikXPap5DHW@pevik \
--to=pvorel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox