public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
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 20:15:43 +0100	[thread overview]
Message-ID: <20181211191543.GA5389@rei> (raw)
In-Reply-To: <20181211184334.GD221175@gmail.com>

Hi!
> No it doesn't really make sense to run a test twice, but this has two associated
> CVE numbers, resulting in two runs when tests are run by CVE number.  Are you
> saying you'd prefer that it be listed under just the more recent CVE?  Or are
> you saying the runtest/cve file will be going away and replaced by something
> else anyway?

For now I would just put it under the newer CVE number.

For a future I would like to be able to export all the metadata from the
tests to the tesrunner, so the testrunner would know, among other
things, which tests are associated with CVEs. That, in turn, would
eliminate the need to maintain various different sets of runtest files.

But given that I just started to work on that I do not expect it to be
finished anytime soon.

Does that sounds reasonable to you?

Also no need to resent the patchset, I can remove the runtest entry when
applying the patch.

-- 
Cyril Hrubis
chrubis@suse.cz

  reply	other threads:[~2018-12-11 19:15 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
2018-12-11 18:43     ` Eric Biggers
2018-12-11 19:15       ` Cyril Hrubis [this message]
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=20181211191543.GA5389@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox