From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] Test for CVE-2016-7042 in /proc/keys show function
Date: Fri, 18 Aug 2017 16:52:56 +0200 [thread overview]
Message-ID: <20170818145256.GF22319@rei.lan> (raw)
In-Reply-To: <87lgnd9bxh.fsf@our.domain.is.not.set>
Hi!
I've created the lapi header meanwhile and so we can make use of it here
but moreover, shouldn't we put this one into the syscalls/keyctl/
directory as we did with previous test and add only runtest CVE entry?
I guess that it makes sense to put syscall tests to syscalls/foo/
directories in a case that we can clearly say that the bug was present
in a particual syscall...
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2017-08-18 14:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 6:03 [LTP] [PATCH] Test for CVE-2016-7042 in /proc/keys show function Guangwen Feng
2017-07-25 8:07 ` Richard Palethorpe
2017-07-26 2:57 ` Guangwen Feng
2017-07-26 3:21 ` [LTP] [PATCH v2] " Guangwen Feng
2017-08-03 5:29 ` [LTP] [PATCH v3] " Guangwen Feng
2017-08-18 15:05 ` Cyril Hrubis
2017-08-18 14:52 ` Cyril Hrubis [this message]
2017-08-18 14:54 ` [LTP] [PATCH] " 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=20170818145256.GF22319@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