netdev - Re: [PATCH net-next v2] mctp: Specify route types, require rtm_type in RTM

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] [day] [month] [year] [list]

Date:   Wed, 11 Aug 2021 23:20:06 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Jeremy Kerr <jk@...econstruct.com.au>
Cc:     netdev@...r.kernel.org, matt@...econstruct.com.au,
        davem@...emloft.net, kuba@...nel.org
Subject: Re: [PATCH net-next v2] mctp: Specify route types,
 require rtm_type in RTM_*ROUTE messages

Hello:

This patch was applied to netdev/net-next.git (refs/heads/master):

On Tue, 10 Aug 2021 10:38:34 +0800 you wrote:
> This change adds a 'type' attribute to routes, which can be parsed from
> a RTM_NEWROUTE message. This will help to distinguish local vs. peer
> routes in a future change.
> 
> This means userspace will need to set a correct rtm_type in RTM_NEWROUTE
> and RTM_DELROUTE messages; we currently only accept RTN_UNICAST.
> 
> [...]

Here is the summary with links:
  - [net-next,v2] mctp: Specify route types, require rtm_type in RTM_*ROUTE messages
    https://git.kernel.org/netdev/net-next/c/83f0a0b7285b

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