From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [RFC PATCH 2/5] runtest/syscalls: rename CVE test cases
Date: Mon, 8 Oct 2018 12:16:56 +0200 [thread overview]
Message-ID: <20181008101656.GB23981@rei.lan> (raw)
In-Reply-To: <94f442a7-e9ff-6377-40ce-fd81e32ae19b@oracle.com>
Hi!
> should I rename them right into testcases/cve or move to a corresponding
> directory in testcases/kernel/syscalls?
>
> I.e.
>
> testcases/cve/cve-2017-6951.c -> testcases/cve/request_key05.c
>
> or
>
> testcases/cve/cve-2017-6951.c ->
> testcases/kernel/syscalls/request_key/request_key05.c
>
> ?
>
> I assume you propose the latter option, correct?
Yes.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2018-10-08 10:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-13 14:44 [LTP] [RFC] Unique test case ids in runtest files ? Stanislav Kholmanskikh
2018-09-13 14:44 ` [LTP] [RFC PATCH 1/5] Remove the pipes runtest file Stanislav Kholmanskikh
2018-10-02 13:12 ` Cyril Hrubis
2018-09-13 14:44 ` [LTP] [RFC PATCH 2/5] runtest/syscalls: rename CVE test cases Stanislav Kholmanskikh
2018-10-02 12:53 ` Cyril Hrubis
2018-10-02 16:19 ` Stanislav Kholmanskikh
2018-10-08 9:52 ` Stanislav Kholmanskikh
2018-10-08 10:16 ` Cyril Hrubis [this message]
2018-09-13 14:44 ` [LTP] [RFC PATCH 3/5] runtest/sched: removed sched_{set, get}attr " Stanislav Kholmanskikh
2018-10-02 12:55 ` Cyril Hrubis
2018-09-13 14:44 ` [LTP] [RFC PATCH 4/5] runtest/commands: adjust names for keyctl01, sysctl01, unshare01 Stanislav Kholmanskikh
2018-10-02 13:03 ` Cyril Hrubis
2018-10-02 16:21 ` Stanislav Kholmanskikh
2018-10-03 7:42 ` Cyril Hrubis
2018-10-08 9:01 ` Stanislav Kholmanskikh
2018-10-08 9:02 ` Cyril Hrubis
2018-09-13 14:44 ` [LTP] [RFC PATCH 5/5] runtest/numa: remove move_pages* test cases Stanislav Kholmanskikh
2018-10-02 13:09 ` Cyril Hrubis
2018-10-02 16:25 ` Stanislav Kholmanskikh
2018-10-02 12:51 ` [LTP] [RFC] Unique test case ids in runtest files ? 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=20181008101656.GB23981@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