public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] cve: add CVE-2025-38236 test
Date: Tue, 12 Aug 2025 13:09:11 +0200	[thread overview]
Message-ID: <aJsg11G8hOAqoGkw@yuki.lan> (raw)
In-Reply-To: <20250812101237.GA835467@pevik>

Hi!
> >  testcases/cve/.gitignore       |   1 +
> >  testcases/cve/cve-2025-38236.c | 101 +++++++++++++++++++++++++++++++++++++++++
> 
> File not added into runtest/cve.
> 
> Maybe we need to enhance 'make check' to check this via 'git grep'.
> 
> checkpatch.pl looks into resulted file, IMHO we have no tool to check the patch
> itself. But maybe enhance b4 (kind of plugin) to check this :).

Or we can genereate the cve runtest file. It should be possible to build
it from the metadata during the build.

-- 
Cyril Hrubis
chrubis@suse.cz

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2025-08-12 11:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-12  8:45 [LTP] [PATCH] cve: add CVE-2025-38236 test Andrea Cervesato
2025-08-12  9:43 ` Wei Gao via ltp
2025-08-12 10:57   ` Andrea Cervesato via ltp
2025-08-12 11:09     ` Petr Vorel
2025-08-12 10:12 ` Petr Vorel
2025-08-12 11:09   ` Cyril Hrubis [this message]
2025-08-12 11:45     ` [LTP] [doc, runtest] [was: Re: [PATCH] cve: add CVE-2025-38236 test] Petr Vorel
2025-08-12 12:09       ` Cyril Hrubis
2025-08-18  6:08         ` Petr Vorel
2025-08-12 10:51 ` [LTP] [PATCH] cve: add CVE-2025-38236 test Petr Vorel
2025-08-12 10:55   ` Andrea Cervesato via ltp
2025-08-12 11:14     ` Cyril Hrubis
2025-08-12 11:17       ` Andrea Cervesato via ltp
2025-08-12 11:50       ` Petr Vorel
2025-08-12 11:25     ` Petr Vorel

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=aJsg11G8hOAqoGkw@yuki.lan \
    --to=chrubis@suse.cz \
    --cc=ltp@lists.linux.it \
    --cc=pvorel@suse.cz \
    /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