From: Richard Palethorpe <rpalethorpe@suse.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 3/4] CVE-2012-0957: Use SAFE_PERSONALITY
Date: Tue, 18 Jul 2017 09:33:18 +0200 [thread overview]
Message-ID: <20170718073319.23543-4-rpalethorpe@suse.com> (raw)
In-Reply-To: <20170718073319.23543-1-rpalethorpe@suse.com>
Signed-off-by: Richard Palethorpe <rpalethorpe@suse.com>
---
testcases/cve/cve-2012-0957.c | 8 ++------
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/testcases/cve/cve-2012-0957.c b/testcases/cve/cve-2012-0957.c
index f065735a1..3b92325d6 100644
--- a/testcases/cve/cve-2012-0957.c
+++ b/testcases/cve/cve-2012-0957.c
@@ -26,10 +26,8 @@
#include <string.h>
#include <sys/utsname.h>
-#include <sys/personality.h>
#include "tst_test.h"
-
-#define UNAME26 0x0020000
+#include "tst_personality.h"
static int check_field(char *bytes, size_t length, char *field)
{
@@ -75,9 +73,7 @@ static void run(unsigned int test_nr)
tst_res(TINFO, "Calling uname with default personality");
try_leak_bytes();
} else {
- if (personality(PER_LINUX | UNAME26) < 0)
- tst_brk(TCONF | TERRNO,
- "Could not change personality to UNAME26");
+ SAFE_PERSONALITY(PER_LINUX | UNAME26);
tst_res(TINFO, "Calling uname with UNAME26 personality");
try_leak_bytes();
}
--
2.13.2
next prev parent reply other threads:[~2017-07-18 7:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 7:33 [LTP] [PATCH 0/4] CVE-2016-10044 and SAFE_PERSONALITY Richard Palethorpe
2017-07-18 7:33 ` [LTP] [PATCH 1/4] configure.ac: Add check for aio_abi.h Richard Palethorpe
2017-07-18 7:33 ` [LTP] [PATCH 2/4] lib: Add personality fallback and SAFE macro Richard Palethorpe
2017-07-18 7:33 ` Richard Palethorpe [this message]
2017-07-18 7:33 ` [LTP] [PATCH 4/4] Test for CVE-2016-10044 mark AIO pseudo-fs noexec Richard Palethorpe
2017-07-18 7:58 ` Jan Stancek
2017-07-18 9:09 ` Richard Palethorpe
2017-07-18 13:40 ` Cyril Hrubis
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=20170718073319.23543-4-rpalethorpe@suse.com \
--to=rpalethorpe@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox