netdev - Re: [PATCH net 0/2] Correct the IOAM behavior for undefined trace type bits

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 12 Oct 2021 11:00:07 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Justin Iurman <justin.iurman@...ege.be>
Cc:     netdev@...r.kernel.org, davem@...emloft.net, kuba@...nel.org,
        yoshfuji@...ux-ipv6.org, dsahern@...nel.org
Subject: Re: [PATCH net 0/2] Correct the IOAM behavior for undefined trace type
 bits

Hello:

This series was applied to netdev/net.git (master)
by David S. Miller <davem@...emloft.net>:

On Mon, 11 Oct 2021 20:04:10 +0200 you wrote:
> (@Jakub @David: there will be a conflict for #2 when merging net->net-next, due
> to commit [1]. The conflict is only 5-10 lines for #2 (#1 should be fine) inside
> the file tools/testing/selftests/net/ioam6.sh, so quite short though possibly
> ugly. Sorry for that, I didn't expect to post this one... Had I known, I'd have
> made the opposite.)
> 
> Modify both the input and output behaviors regarding the trace type when one of
> the undefined bits is set. The goal is to keep the interoperability when new
> fields (aka new bits inside the range 12-21) will be defined.
> 
> [...]

Here is the summary with links:
  - [net,1/2] ipv6: ioam: move the check for undefined bits
    https://git.kernel.org/netdev/net/c/2bbc977ca689
  - [net,2/2] selftests: net: modify IOAM tests for undef bits
    https://git.kernel.org/netdev/net/c/7b1700e009cc

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html