From: Sachin Sant <sachinp@linux.ibm.com>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v4 1/2] doc: generate CVE catalog documentation
Date: Thu, 7 May 2026 15:44:02 +0530 [thread overview]
Message-ID: <f5cb3a8d-8feb-45e7-b02b-2871808ac38e@linux.ibm.com> (raw)
In-Reply-To: <aftwmBUir04jaik4@yuki.lan>
On 06/05/26 10:17 pm, Cyril Hrubis wrote:
> Hi!
>> - rm -rf html/ build/ _static/syscalls.rst _static/tests.rst syscalls.tbl \
>> + rm -rf html/ build/ _static/syscalls.rst _static/tests.rst _static/cve.rst syscalls.tbl \
>> ${abs_top_builddir}/metadata/ltp.json
> This shouldn't be added here. the ltp.json is cleaned up by the
> metadata/Makefile.
My bad, probably an oversight on my part. Will remove.
>> + Generate CVE catalog in a single file. Parse runtest/cve file and
>> + generate documentation with links to CVE databases and test sources.
>> + Similar to test_catalog, creates a single _static/cve.rst file with
>> + all CVE information.
>> + """
>> + output = '_static/cve.rst'
>> + runtest_cve = '../runtest/cve'
> I do not like much that we depend on the cve runtest file, we want to
> get rid of runtest files eventually and depend only on the ltp.json.
Ah I see. Thanks for the review. Will remove the dependency on runtest/cve.
>> + text.extend([
>> + f' * - {cve_id}',
>> + f' - {test_link}',
>> + ])
> Can we please instead iterate over the "tests" in the metadata here and
> collect all tests that have "CVE" key in "tags"?
>
> That should be more straightforward since we do not need to parse two
> files.
Sure, will rewrite the logic based on ltp.json metadata.
Will send an updated version of the patch.
--
Thanks
- Sachin
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-05-07 10:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 14:36 [LTP] [PATCH v4 1/2] doc: generate CVE catalog documentation Sachin Sant
2026-04-28 14:36 ` [LTP] [PATCH 2/2] doc: Rename statistics page to 'Supported syscalls' Sachin Sant
2026-04-29 7:21 ` Andrea Cervesato via ltp
2026-04-28 16:55 ` [LTP] doc: generate CVE catalog documentation linuxtestproject.agent
2026-04-29 7:20 ` [LTP] [PATCH v4 1/2] " Andrea Cervesato via ltp
2026-05-06 16:05 ` Andrea Cervesato via ltp
2026-05-06 16:47 ` Cyril Hrubis
2026-05-07 10:14 ` Sachin Sant [this message]
2026-05-07 10:30 ` Sachin Sant
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=f5cb3a8d-8feb-45e7-b02b-2871808ac38e@linux.ibm.com \
--to=sachinp@linux.ibm.com \
--cc=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