All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Geliang Tang <geliangtang@gmail.com>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next 2/7] selftests: mptcp: add missing kconfig for NF Filter in v6
Date: Tue, 30 Jan 2024 10:59:03 +0100	[thread overview]
Message-ID: <625fa4fe-6ecf-4185-bc43-a268f55a3bf9@kernel.org> (raw)
In-Reply-To: <CA+WQbwtkbYkxMkfhs0yUOx5RnJ2_ftNf7i0URMpcBL7qK7GdhQ@mail.gmail.com>

Hi Geliang,

Thank you for the review!

Hi Geliang,

Thank you for the review!

On 22/01/2024 02:47, Geliang Tang wrote:
>> Since the commit mentioned below, 'mptcp_join' selftests is using
>> IPTables to add rules to the Filter table for IPv6.
>>
>> It is then required to have IP6_NF_FILTER KConfig.
>>
>> This KConfig is usually enabled by default in many defconfig, but we
>> recently noticed that some CI were running our selftests without them
>> enabled.
>>
>> Fixes: 523514ed0a99 ("selftests: mptcp: add ADD_ADDR IPv6 test cases")
>> Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
>> ---
>>  tools/testing/selftests/net/mptcp/config | 1 +
>>  1 file changed, 1 insertion(+)
>>
>> diff --git a/tools/testing/selftests/net/mptcp/config b/tools/testing/selftests/net/mptcp/config
>> index 2a00bf4acdfa..ec70b27288fc 100644
>> --- a/tools/testing/selftests/net/mptcp/config
>> +++ b/tools/testing/selftests/net/mptcp/config
>> @@ -20,6 +20,7 @@ CONFIG_NETFILTER_XT_TARGET_MARK=m
>>  CONFIG_NF_TABLES_INET=y
>>  CONFIG_NFT_TPROXY=m
>>  CONFIG_NFT_SOCKET=m
>> +CONFIG_IP6_NF_FILTER=m
> 
> How about adding this config right after CONFIG_IP_NF_TARGET_REJECT=m?
> 
> Since "IPv6: Netfilter Configuration" section in kconfig is always
> after "IP: Netfilter Configuration" one.

My intension was to place this new entry there to keep the file sorted
by alphabetical order. It is often recommended to do that for that kind
of files to ease the backports. So I put it before "IP_ADVANCED_ROUTER".

But now, I realise this file is not fully sorted by alphabetical order :)

I don't think the order matter, but I can place it after
"IPV6_MULTIPLE_TABLES". I can do that when applying the patches: I don't
think I need to send a v2 just for that.

Cheers,
Matt
-- 
Sponsored by the NGI0 Core fund.

  reply	other threads:[~2024-01-30  9:59 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-18 18:27 [PATCH mptcp-next 0/7] selftests: mptcp: improve results in slow CI envs Matthieu Baerts (NGI0)
2024-01-18 18:27 ` [PATCH mptcp-next 1/7] selftests: mptcp: add missing kconfig for NF Filter Matthieu Baerts (NGI0)
2024-01-18 18:27 ` [PATCH mptcp-next 2/7] selftests: mptcp: add missing kconfig for NF Filter in v6 Matthieu Baerts (NGI0)
2024-01-22  1:47   ` Geliang Tang
2024-01-30  9:59     ` Matthieu Baerts [this message]
2024-01-18 18:27 ` [PATCH mptcp-next 3/7] selftests: mptcp: add missing kconfig for NF Mangle Matthieu Baerts (NGI0)
2024-01-18 18:27 ` [PATCH mptcp-next 4/7] selftests: mptcp: increase timeout to 30 min Matthieu Baerts (NGI0)
2024-01-23 20:53   ` Paolo Abeni
2024-01-18 18:27 ` [PATCH mptcp-next 5/7] selftests: mptcp: decrease BW in simult flows Matthieu Baerts (NGI0)
2024-01-18 18:27 ` [PATCH mptcp-next 6/7] selftests: mptcp: allow changing subtests prefix Matthieu Baerts (NGI0)
2024-01-18 18:27 ` [PATCH mptcp-next 7/7] selftests: mptcp: join: stop transfer when check is done Matthieu Baerts (NGI0)
2024-01-18 19:36   ` selftests: mptcp: join: stop transfer when check is done: Tests Results MPTCP CI
2024-01-18 19:53   ` MPTCP CI
2024-01-22  1:02   ` [PATCH mptcp-next 7/7] selftests: mptcp: join: stop transfer when check is done Geliang Tang
2024-01-22  3:00   ` selftests: mptcp: join: stop transfer when check is done: Tests Results MPTCP CI
2024-01-22  3:54   ` MPTCP CI
2024-01-23 22:05   ` MPTCP CI
2024-01-23 23:23   ` MPTCP CI
2024-01-30 12:14 ` [PATCH mptcp-next 0/7] selftests: mptcp: improve results in slow CI envs Matthieu Baerts

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=625fa4fe-6ecf-4185-bc43-a268f55a3bf9@kernel.org \
    --to=matttbe@kernel.org \
    --cc=geliangtang@gmail.com \
    --cc=mptcp@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.