From: patchwork-bot+netdevbpf@kernel.org
To: Colin Ian King <colin.king@canonical.com>
Cc: sgoutham@marvell.com, davem@davemloft.net, kuba@kernel.org,
ganapatrao.kulkarni@caviumnetworks.com, david.daney@cavium.com,
svangala@cavium.com, tsrinivasulu@caviumnetworks.com,
linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: thunderx: Fix unintentional sign extension issue
Date: Mon, 12 Apr 2021 20:20:08 +0000 [thread overview]
Message-ID: <161825880887.1346.11596655945494608028.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210409130726.665490-1-colin.king@canonical.com>
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Fri, 9 Apr 2021 14:07:26 +0100 you wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> The shifting of the u8 integers rq->caching by 26 bits to
> the left will be promoted to a 32 bit signed int and then
> sign-extended to a u64. In the event that rq->caching is
> greater than 0x1f then all then all the upper 32 bits of
> the u64 end up as also being set because of the int
> sign-extension. Fix this by casting the u8 values to a
> u64 before the 26 bit left shift.
>
> [...]
Here is the summary with links:
- net: thunderx: Fix unintentional sign extension issue
https://git.kernel.org/netdev/net-next/c/e701a2584036
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-04-12 20:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 13:07 [PATCH] net: thunderx: Fix unintentional sign extension issue Colin King
2021-04-12 20:20 ` patchwork-bot+netdevbpf [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=161825880887.1346.11596655945494608028.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=colin.king@canonical.com \
--cc=davem@davemloft.net \
--cc=david.daney@cavium.com \
--cc=ganapatrao.kulkarni@caviumnetworks.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sgoutham@marvell.com \
--cc=svangala@cavium.com \
--cc=tsrinivasulu@caviumnetworks.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox