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: 
 <172078803199.14799.923781720410892219.git-patchwork-notify@kernel.org>
Date: Fri, 12 Jul 2024 12:40:31 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Jeremy Kerr <jk@...econstruct.com.au>
Cc: matt@...econstruct.com.au, davem@...emloft.net, edumazet@...gle.com,
 kuba@...nel.org, pabeni@...hat.com, netdev@...r.kernel.org,
 Bonnie_Lo@...ynn.com, Jerry_C_Chen@...ynn.com
Subject: Re: [PATCH net-next] net: mctp-i2c: invalidate flows immediately on TX
 errors

Hello:

This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@...emloft.net>:

On Wed, 10 Jul 2024 10:17:22 +0800 you wrote:
> If we encounter an error on i2c packet transmit, we won't have a valid
> flow anymore; since we didn't transmit a valid packet sequence, we'll
> have to wait for the key to timeout instead of dropping it on the reply.
> 
> This causes the i2c lock to be held for longer than necessary.
> 
> Instead, invalidate the flow on TX error, and release the i2c lock
> immediately.
> 
> [...]

Here is the summary with links:
  - [net-next] net: mctp-i2c: invalidate flows immediately on TX errors
    https://git.kernel.org/netdev/net-next/c/338a93cf4a18

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



Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ