netdev - Re: [PATCH net-next v2] net: octeontx2: Fix the confusion in buffer alloc failure path

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: <161299920743.13771.4953397169592654903.git-patchwork-notify@kernel.org>
Date:   Wed, 10 Feb 2021 23:20:07 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Kevin Hao <haokexin@...il.com>
Cc:     davem@...emloft.net, kuba@...nel.org, sgoutham@...vell.com,
        gakula@...vell.com, sbhatta@...vell.com, hkelam@...vell.com,
        netdev@...r.kernel.org, pavel@....cz
Subject: Re: [PATCH net-next v2] net: octeontx2: Fix the confusion in buffer alloc
 failure path

Hello:

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

On Tue,  9 Feb 2021 18:15:16 +0800 you wrote:
> Pavel pointed that the return of dma_addr_t in
> otx2_alloc_rbuf/__otx2_alloc_rbuf() seem suspicious because a negative
> error code may be returned in some cases. For a dma_addr_t, the error
> code such as -ENOMEM does seem a valid value, so we can't judge if the
> buffer allocation fail or not based on that value. Add a parameter for
> otx2_alloc_rbuf/__otx2_alloc_rbuf() to store the dma address and make
> the return value to indicate if the buffer allocation really fail or
> not.
> 
> [...]

Here is the summary with links:
  - [net-next,v2] net: octeontx2: Fix the confusion in buffer alloc failure path
    https://git.kernel.org/netdev/net-next/c/1fb3ca767529

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