From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2 1/2] lib: Add support for test tags
Date: Wed, 23 Oct 2019 18:06:40 +0200 [thread overview]
Message-ID: <20191023160640.GA17663@rei> (raw)
In-Reply-To: <CAEemH2f2D4PjaMaOE_ADUqg5igEi97nHBsH6A7qXtO-2KO7btg@mail.gmail.com>
Hi!
> Sorry, thanks for the reminder.
> [I copied the below code to gmail, it always lost the indent]
>
> static void print_failure_hints(void)
> {
> unsigned int i;
> int hint_printed = 0;
> const struct tst_tag *tags = tst_test->tags;
>
> if (!tags)
> return;
>
> for (i = 0; tags[i].name; i++) {
> if (!strcmp(tags[i].name, "linux-git")) {
> if (hint_printed != 1) {
> hint_printed = 1;
> print_colored("\nHINT: ");
> printf("You _MAY_ be missing kernel fixes,
> see:\n\n");
> }
>
> printf(LINUX_GIT_URL "%s\n", tags[i].value);
> } else if (!strcmp(tags[i].name, "CVE")) {
> if (hint_printed != 2) {
> hint_printed = 2;
> print_colored("\nHINT: ");
> printf("You _MAY_ be vunerable to CVE(s),
> see:\n\n");
> }
>
> printf(CVE_DB_URL "%s\n", tags[i].value);
This would produce intermixed CVE and linux-git lines unless the tags
are sorted correctly in the source code, I do not want to depend on the
order hence the two loops.
> } else {
> print_colored("\nERROR: ");
> printf("tags[%d].name should be linux-git or
> CVE\n", i);
> return;
I've tried to explain to pvorel already that this is a wrong place to
assert the tag names. If nothing else this piece of code will be rarely
triggered and the error would end up ignored.
I plan to assert the tag names in the docparse tool that will build the
test metadata during the LTP build, so that wrong metadata will actually
fail the LTP build.
> }
> }
> }
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2019-10-23 16:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-22 14:07 [LTP] [PATCH v2 0/2] Add support for a test tags Cyril Hrubis
2019-10-22 14:07 ` [LTP] [PATCH v2 1/2] lib: Add support for " Cyril Hrubis
2019-10-22 14:19 ` Petr Vorel
2019-11-06 15:26 ` Cyril Hrubis
2019-10-23 7:39 ` Li Wang
2019-10-23 7:58 ` Jan Stancek
2019-10-23 8:06 ` Li Wang
2019-10-23 16:06 ` Cyril Hrubis [this message]
2019-10-24 2:45 ` Li Wang
2019-10-22 14:07 ` [LTP] [PATCH v2 2/2] testcases/kernel: Add linux git and CVE tags Cyril Hrubis
2019-10-23 7:18 ` Li Wang
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=20191023160640.GA17663@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