Re: [PATCH net-next 1/5] can: isotp: sanitize CAN ID checks in isotp_bind()

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello:

This series was applied to netdev/net-next.git (master)
by Marc Kleine-Budde <mkl@xxxxxxxxxxxxxx>:

On Wed, 16 Mar 2022 21:47:06 +0100 you wrote:
> From: Oliver Hartkopp <socketcan@xxxxxxxxxxxx>
> 
> Syzbot created an environment that lead to a state machine status that
> can not be reached with a compliant CAN ID address configuration.
> The provided address information consisted of CAN ID 0x6000001 and 0xC28001
> which both boil down to 11 bit CAN IDs 0x001 in sending and receiving.
> 
> [...]

Here is the summary with links:
  - [net-next,1/5] can: isotp: sanitize CAN ID checks in isotp_bind()
    https://git.kernel.org/netdev/net-next/c/3ea566422cbd
  - [net-next,2/5] can: isotp: return -EADDRNOTAVAIL when reading from unbound socket
    https://git.kernel.org/netdev/net-next/c/30ffd5332e06
  - [net-next,3/5] can: isotp: support MSG_TRUNC flag when reading from socket
    https://git.kernel.org/netdev/net-next/c/42bf50a1795a
  - [net-next,4/5] dt-bindings: can: xilinx_can: Convert Xilinx CAN binding to YAML
    https://git.kernel.org/netdev/net-next/c/7843d3c8e5e6
  - [net-next,5/5] can: ucan: fix typos in comments
    https://git.kernel.org/netdev/net-next/c/c34983c94166

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





[Index of Archives]     [Automotive Discussions]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]     [CAN Bus]

  Powered by Linux