Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Justin Iurman <justin.iurman@uliege.be>
To: Paolo Abeni <pabeni@redhat.com>, netdev@vger.kernel.org
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	shuah@kernel.org, linux-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next] selftests: net: ioam: add tunsrc support
Date: Mon, 23 Sep 2024 11:22:12 +0200	[thread overview]
Message-ID: <e9cf1bf8-2d77-4165-bf64-b41f3b8b880d@uliege.be> (raw)
In-Reply-To: <bbeb8c77-1772-45a2-8626-a4e064ab7c54@redhat.com>

On 9/19/24 09:57, Paolo Abeni wrote:
> On 9/7/24 18:42, Justin Iurman wrote:
>> TL;DR This patch comes from a discussion we had with Jakub and Paolo.
>>
>> This patch updates the IOAM selftests to support the new "tunsrc"
>> feature of IOAM. As a consequence, some changes were required. For
>> example, the IPv6 header must be accessed to check some fields (i.e.,
>> the source address for the "tunsrc" feature), which is not possible
>> AFAIK with IPv6 raw sockets. The latter is currently used with
>> IPV6_RECVHOPOPTS and was introduced by commit 187bbb6968af ("selftests:
>> ioam: refactoring to align with the fix") to fix an issue. But, we
>> really need packet sockets actually... which is one of the changes in
>> this patch (see the description of the topology at the top of ioam6.sh
>> for explanations). Another change is that all IPv6 addresses used in the
>> topology are now based on the documentation prefix (2001:db8::/32).
>> Also, the tests have been improved and there are now many more of them.
>> Overall, the script is more robust.
>>
>> The diff is kind of a mess. Since it's "just" a selftests patch, I
>> didn't bother having a series of two patches (one to remove it, one to
>> add the new one back). Let me know if you think it's necessary for
>> readability.
>>
>> Note: this patch needs this [1] iproute2-next patch to be merged
>> (waiting for David to do so, should be done soon).
>>
>>    [1] https://patchwork.kernel.org/project/netdevbpf/list/?series=884653
>>
>> Signed-off-by: Justin Iurman <justin.iurman@uliege.be>
> 
> Unfortunatelly we was unable to process this patch before the merge 
> window and net-next is currently closed. You will need to repost it is ~2w.

Hi Paolo,

Sure, no worries.

> Strictly speaking about the patch contents, any chance you could 
> refactor the change in a more 'incremental' way?
> The current format is very hard to review, and even self-tests patches 
> deserve some love ;)

I think the best incremental way I can come up with right now (so that 
it also makes my life easier) is to have a series that (i) removes the 
ioam selftests (patch #1) and (ii) re-adds the new one (patch #2). Would 
you all agree with this?

Cheers,
Justin

> Thanks,
> 
> Paolo
> 

      reply	other threads:[~2024-09-23  9:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-07 16:42 [PATCH net-next] selftests: net: ioam: add tunsrc support Justin Iurman
2024-09-19  7:57 ` Paolo Abeni
2024-09-23  9:22   ` Justin Iurman [this message]

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=e9cf1bf8-2d77-4165-bf64-b41f3b8b880d@uliege.be \
    --to=justin.iurman@uliege.be \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=shuah@kernel.org \
    /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