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]
Date:   Wed, 20 Jul 2022 10:20:13 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Alex Elder <elder@...aro.org>
Cc:     davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
        pabeni@...hat.com, mka@...omium.org, evgreen@...omium.org,
        bjorn.andersson@...aro.org, quic_cpratapa@...cinc.com,
        quic_avuyyuru@...cinc.com, quic_jponduru@...cinc.com,
        quic_subashab@...cinc.com, elder@...nel.org,
        netdev@...r.kernel.org, linux-arm-msm@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next] net: ipa: initialize ring indexes to 0

Hello:

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

On Tue, 19 Jul 2022 09:18:55 -0500 you wrote:
> When a GSI channel is initially allocated, and after it has been
> reset, the hardware assumes its ring index is 0.  And although we
> do initialize channels this way, the comments in the IPA code don't
> really explain this.  For event rings, it doesn't matter what value
> we use initially, so using 0 is just fine.
> 
> Add some information about the assumptions made by hardware above
> the definition of the gsi_ring structure in "gsi.h".
> 
> [...]

Here is the summary with links:
  - [net-next] net: ipa: initialize ring indexes to 0
    https://git.kernel.org/netdev/net-next/c/5fb859f79f4f

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