From: Cyril Hrubis <chrubis@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.de>
Cc: Linux Test Project <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH v3 1/2] tst_kconfig: add module mappings for ingress/matchall/pedit
Date: Mon, 20 Jul 2026 17:31:37 +0200 [thread overview]
Message-ID: <al4_WWeLFMSvL0tS@yuki.lan> (raw)
In-Reply-To: <20260720-fix_cve-2026-46331_enoent-v3-1-9f216efdd661@suse.com>
Hi!
> Map CONFIG_NET_SCH_INGRESS, CONFIG_NET_CLS_MATCHALL and CONFIG_NET_ACT_PEDIT
> to their kernel modules (sch_ingress, cls_matchall, act_pedit).
>
> Signed-off-by: Andrea Cervesato <andrea.cervesato@suse.com>
> ---
> lib/tst_kconfig.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/lib/tst_kconfig.c b/lib/tst_kconfig.c
> index 44eacc7c2989a5af3347b8f7ed16393fde0122a6..277ac606895046e072cf8f86076ecf7d79f9b1e6 100644
> --- a/lib/tst_kconfig.c
> +++ b/lib/tst_kconfig.c
> @@ -162,6 +162,9 @@ static struct config_module_map {
> {"CONFIG_CAN_RAW", "can-raw"},
> {"CONFIG_CAN_BCM", "can-bcm"},
> {"CONFIG_IP_SCTP", "sctp"},
> + {"CONFIG_NET_SCH_INGRESS", "sch_ingress"},
> + {"CONFIG_NET_CLS_MATCHALL", "cls_matchall"},
> + {"CONFIG_NET_ACT_PEDIT", "act_pedit"},
> {}
> };
This is still missing the additions to the CONFIG -> module map.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-07-20 15:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 14:31 [LTP] [PATCH v3 0/2] Fix cve-2026-46331 producing ENOENT Andrea Cervesato
2026-07-20 14:31 ` [LTP] [PATCH v3 1/2] tst_kconfig: add module mappings for ingress/matchall/pedit Andrea Cervesato
2026-07-20 15:31 ` Cyril Hrubis [this message]
2026-07-20 15:55 ` [LTP] " linuxtestproject.agent
2026-07-20 14:31 ` [LTP] [PATCH v3 2/2] cve-2026-46331: fix intermittent ENOENT failure Andrea Cervesato
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=al4_WWeLFMSvL0tS@yuki.lan \
--to=chrubis@suse.cz \
--cc=andrea.cervesato@suse.de \
--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