From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v4 6/7] Convert cve-2014-0196 to use long running threads
Date: Tue, 26 Sep 2017 12:05:27 +0200 [thread overview]
Message-ID: <20170926100527.GB4884@rei.lan> (raw)
In-Reply-To: <20170925095137.31491-6-rpalethorpe@suse.com>
Hi!
I'm getting warnings for this testcase on SLES12 SP2:
tst_test.c:934: INFO: Timeout per run is 0h 05m 00s
cve-2014-0196.c:103: INFO: Attempting to overflow into a tty_struct...
safe_macros.c:452: BROK: cve-2014-0196.c:90: write(-1,0x6156a0,18446744073709551615) failed: EBADF
cve-2014-0196.c:154: WARN: pthread_join(..., (nil)) failed: EDEADLK
Looks like the SAFE_WRITE() in the overwrite_thread_fn() races with the
SAFE_CLOSE() in the run() function.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2017-09-26 10:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 9:51 [LTP] [PATCH v4 1/7] tst_atomic: Add load, store and use __atomic builtins Richard Palethorpe
2017-09-25 9:51 ` [LTP] [PATCH v4 2/7] tst_atomic: Add atomic store and load tests Richard Palethorpe
2017-09-25 9:51 ` [LTP] [PATCH v4 3/7] fzsync: Add long running thread support and deviation stats Richard Palethorpe
2017-09-25 16:04 ` Cyril Hrubis
2017-09-29 9:44 ` Richard Palethorpe
2017-09-25 9:51 ` [LTP] [PATCH v4 4/7] fzsync: Add functionality test for library Richard Palethorpe
2017-09-25 9:51 ` [LTP] [PATCH v4 5/7] Convert cve-2016-7117 test to use long running threads Richard Palethorpe
2017-09-25 9:51 ` [LTP] [PATCH v4 6/7] Convert cve-2014-0196 " Richard Palethorpe
2017-09-26 10:05 ` Cyril Hrubis [this message]
2017-09-25 9:51 ` [LTP] [PATCH v4 7/7] Convert cve-2017-2671 " Richard Palethorpe
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=20170926100527.GB4884@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox