From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2 3/3] crypto/crypto_user01.c: new test for information leak bug
Date: Tue, 11 Dec 2018 13:32:52 +0100 [thread overview]
Message-ID: <20181211123251.GA27346@rei> (raw)
In-Reply-To: <20181211060317.18698-4-ebiggers@kernel.org>
Hi!
> --- a/runtest/crypto
> +++ b/runtest/crypto
> @@ -1 +1,2 @@
> pcrypt_aead01 pcrypt_aead01
> +crypto_user01 crypto_user01
> diff --git a/runtest/cve b/runtest/cve
> index c4ba74186..78a5d8db2 100644
> --- a/runtest/cve
> +++ b/runtest/cve
> @@ -3,6 +3,7 @@ cve-2011-0999 thp01 -I 120
> cve-2011-2183 ksm05 -I 10
> cve-2011-2496 vma03
> cve-2012-0957 uname04
> +cve-2013-2547 crypto_user01
> cve-2014-0196 cve-2014-0196
> cve-2015-0235 gethostbyname_r01
> cve-2015-7550 keyctl02
> @@ -36,3 +37,4 @@ cve-2017-17053 cve-2017-17053
> cve-2017-18075 pcrypt_aead01
> cve-2018-5803 sctp_big_chunk
> cve-2018-1000001 realpath01
> +cve-2018-19854 crypto_user01
Does it really make sense to run this test twice just under different
name?
BTW: I'm working on test tags and metadata patches that would make
failed tests print list of CVEs and kernel commits that fixed them on a
failure and also under the -h help switch, which should fix this once
for all.
See:
http://lists.linux.it/pipermail/ltp/2018-November/009895.html
http://lists.linux.it/pipermail/ltp/2018-November/010118.html
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2018-12-11 12:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 6:03 [LTP] [PATCH v2 0/3] ltp: new test for crypto_user information leak bug Eric Biggers
2018-12-11 6:03 ` [LTP] [PATCH v2 1/3] lapi/cryptouser.h: add more declarations Eric Biggers
2018-12-11 6:03 ` [LTP] [PATCH v2 2/3] tst_netlink: inline functions in header Eric Biggers
2018-12-11 6:03 ` [LTP] [PATCH v2 3/3] crypto/crypto_user01.c: new test for information leak bug Eric Biggers
2018-12-11 12:32 ` Cyril Hrubis [this message]
2018-12-11 18:43 ` Eric Biggers
2018-12-11 19:15 ` Cyril Hrubis
2018-12-11 20:52 ` Eric Biggers
2018-12-17 13:01 ` Cyril Hrubis
2018-12-11 8:46 ` [LTP] [PATCH v2 0/3] ltp: new test for crypto_user " 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=20181211123251.GA27346@rei \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.