netdev - Re: [PATCH net] can: isotp: stop timeout monitoring when no first frame was sent

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]

Message-Id: <165027421135.11239.7151679337117584143.git-patchwork-notify@kernel.org>
Date:   Mon, 18 Apr 2022 09:30:11 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Marc Kleine-Budde <mkl@...gutronix.de>
Cc:     netdev@...r.kernel.org, davem@...emloft.net, kuba@...nel.org,
        linux-can@...r.kernel.org, kernel@...gutronix.de,
        socketcan@...tkopp.net,
        syzbot+2339c27f5c66c652843e@...kaller.appspotmail.com
Subject: Re: [PATCH net] can: isotp: stop timeout monitoring when no first frame
 was sent

Hello:

This patch was applied to netdev/net.git (master)
by Marc Kleine-Budde <mkl@...gutronix.de>:

On Sun, 17 Apr 2022 17:29:34 +0200 you wrote:
> From: Oliver Hartkopp <socketcan@...tkopp.net>
> 
> The first attempt to fix a the 'impossible' WARN_ON_ONCE(1) in
> isotp_tx_timer_handler() focussed on the identical CAN IDs created by
> the syzbot reproducer and lead to upstream fix/commit 3ea566422cbd
> ("can: isotp: sanitize CAN ID checks in isotp_bind()"). But this did
> not catch the root cause of the wrong tx.state in the tx_timer handler.
> 
> [...]

Here is the summary with links:
  - [net] can: isotp: stop timeout monitoring when no first frame was sent
    https://git.kernel.org/netdev/net/c/d73497081710

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