netdev - Re: [PATCH iproute2] dcb: Do not leave ACKs in socket receive buffer

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: <167233261544.30800.10653820168692161796.git-patchwork-notify@kernel.org>
Date:   Thu, 29 Dec 2022 16:50:15 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Ido Schimmel <idosch@...dia.com>
Cc:     netdev@...r.kernel.org, stephen@...workplumber.org,
        dsahern@...il.com, chenjunxin1@...wei.com, petrm@...dia.com,
        mlxsw@...dia.com
Subject: Re: [PATCH iproute2] dcb: Do not leave ACKs in socket receive buffer

Hello:

This patch was applied to iproute2/iproute2.git (main)
by Stephen Hemminger <stephen@...workplumber.org>:

On Tue, 27 Dec 2022 13:03:18 +0200 you wrote:
> Originally, the dcb utility only stopped receiving messages from a
> socket when it found the attribute it was looking for. Cited commit
> changed that, so that the utility will also stop when seeing an ACK
> (NLMSG_ERROR message), by setting the NLM_F_ACK flag on requests.
> 
> This is problematic because it means a successful request will leave an
> ACK in the socket receive buffer, causing the next request to bail
> before reading its response.
> 
> [...]

Here is the summary with links:
  - [iproute2] dcb: Do not leave ACKs in socket receive buffer
    https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=d0e02f35af33

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