From: patchwork-bot+netdevbpf@kernel.org
To: Colin King <colin.king@canonical.com>
Cc: iii@linux.ibm.com, hca@linux.ibm.com, gor@linux.ibm.com,
borntraeger@de.ibm.com, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, songliubraving@fb.com, yhs@fb.com,
john.fastabend@gmail.com, kpsingh@kernel.org,
holzheu@linux.vnet.ibm.com, schwidefsky@de.ibm.com,
netdev@vger.kernel.org, bpf@vger.kernel.org,
linux-s390@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] s390/bpf: perform r1 range checking before accessing jit->seen_reg[r1]
Date: Thu, 15 Jul 2021 17:50:04 +0000 [thread overview]
Message-ID: <162637140434.23218.4971515886855258652.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210715125712.24690-1-colin.king@canonical.com>
Hello:
This patch was applied to bpf/bpf.git (refs/heads/master):
On Thu, 15 Jul 2021 13:57:12 +0100 you wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> Currently array jit->seen_reg[r1] is being accessed before the range
> checking of index r1. The range changing on r1 should be performed
> first since it will avoid any potential out-of-range accesses on the
> array seen_reg[] and also it is more optimal to perform checks on
> r1 before fetching data from the array. Fix this by swapping the
> order of the checks before the array access.
>
> [...]
Here is the summary with links:
- s390/bpf: perform r1 range checking before accessing jit->seen_reg[r1]
https://git.kernel.org/bpf/bpf/c/91091656252f
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-07-15 17:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-15 12:57 [PATCH] s390/bpf: perform r1 range checking before accessing jit->seen_reg[r1] Colin King
2021-07-15 17:02 ` Ilya Leoshkevich
2021-07-15 17:50 ` 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=162637140434.23218.4971515886855258652.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=borntraeger@de.ibm.com \
--cc=bpf@vger.kernel.org \
--cc=colin.king@canonical.com \
--cc=daniel@iogearbox.net \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=holzheu@linux.vnet.ibm.com \
--cc=iii@linux.ibm.com \
--cc=john.fastabend@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
--cc=songliubraving@fb.com \
--cc=yhs@fb.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