From: Petr Vorel <pvorel@suse.cz>
To: Martin Doucha <mdoucha@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2 5/5] Add test for CVE 2023-31248
Date: Tue, 14 Nov 2023 16:39:07 +0100 [thread overview]
Message-ID: <20231114153907.GA2357693@pevik> (raw)
In-Reply-To: <20231114123140.1144-6-mdoucha@suse.cz>
Hi Martin,
...
> +++ b/testcases/network/iptables/nft02.c
...
> +/* Chain creation and deletion config */
> +static const struct tst_netlink_attr_list newchain_config[] = {
> + {NFTA_TABLE_NAME, TABNAME, strlen(TABNAME) + 1, NULL},
> + {NFTA_CHAIN_NAME, CHAINNAME, strlen(CHAINNAME) + 1, NULL},
> + {NFTA_CHAIN_ID, &chain_id, sizeof(chain_id), NULL},
Unfortunately the current oldest distros (Leap 42 and Ubuntu Bionic) are too old
for NFTA_CHAIN_ID, NFTA_RULE_CHAIN_ID, could you please add them to LAPI?
Otherwise the patchset looks ok.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-11-14 15:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 12:31 [LTP] [PATCH v2 0/5] Netlink helper functions refactoring + CVE 2023-31248 Martin Doucha
2023-11-14 12:31 ` [LTP] [PATCH v2 1/5] tst_rtnetlink: Refactor helper function for generic use Martin Doucha
2023-11-14 19:14 ` Petr Vorel
2023-11-14 12:31 ` [LTP] [PATCH v2 2/5] tst_netlink_destroy_context(): Allow safely passing NULL context Martin Doucha
2023-11-14 12:31 ` [LTP] [PATCH v2 3/5] crypto: Replace old netlink helper functions with netlink contexts Martin Doucha
2023-11-14 12:31 ` [LTP] [PATCH v2 4/5] tst_netlink: Add helper functions for handling generic attributes Martin Doucha
2023-11-14 12:31 ` [LTP] [PATCH v2 5/5] Add test for CVE 2023-31248 Martin Doucha
2023-11-14 15:39 ` Petr Vorel [this message]
2023-11-15 7:43 ` 河原颯太
2023-11-15 8:23 ` Petr Vorel
2023-11-15 9:16 ` Jan Stancek
2023-11-15 17:34 ` Martin Doucha
2023-11-15 23:39 ` 河原颯太
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=20231114153907.GA2357693@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
--cc=mdoucha@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