BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: davem@davemloft.net, daniel@iogearbox.net, andrii@kernel.org,
	bpf@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH bpf-next 1/2] bpf: Fix combination of jit blinding and pointers to bpf subprogs.
Date: Fri, 13 May 2022 13:20:13 +0000	[thread overview]
Message-ID: <165244801337.11154.3266406533060749854.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220513011025.13344-1-alexei.starovoitov@gmail.com>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:

On Thu, 12 May 2022 18:10:24 -0700 you wrote:
> From: Alexei Starovoitov <ast@kernel.org>
> 
> The combination of jit blinding and pointers to bpf subprogs causes:
> [   36.989548] BUG: unable to handle page fault for address: 0000000100000001
> [   36.990342] #PF: supervisor instruction fetch in kernel mode
> [   36.990968] #PF: error_code(0x0010) - not-present page
> [   36.994859] RIP: 0010:0x100000001
> [   36.995209] Code: Unable to access opcode bytes at RIP 0xffffffd7.
> [   37.004091] Call Trace:
> [   37.004351]  <TASK>
> [   37.004576]  ? bpf_loop+0x4d/0x70
> [   37.004932]  ? bpf_prog_3899083f75e4c5de_F+0xe3/0x13b
> 
> [...]

Here is the summary with links:
  - [bpf-next,1/2] bpf: Fix combination of jit blinding and pointers to bpf subprogs.
    https://git.kernel.org/bpf/bpf-next/c/4b6313cf99b0
  - [bpf-next,2/2] selftests/bpf: Check combination of jit blinding and pointers to bpf subprogs.
    https://git.kernel.org/bpf/bpf-next/c/365d519923a2

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



      parent reply	other threads:[~2022-05-13 13:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-13  1:10 [PATCH bpf-next 1/2] bpf: Fix combination of jit blinding and pointers to bpf subprogs Alexei Starovoitov
2022-05-13  1:10 ` [PATCH bpf-next 2/2] selftests/bpf: Check " Alexei Starovoitov
2022-05-13  3:45   ` Andrii Nakryiko
2022-05-13  5:48   ` Martin KaFai Lau
2022-05-13  3:44 ` [PATCH bpf-next 1/2] bpf: Fix " Andrii Nakryiko
2022-05-13  3:45   ` Alexei Starovoitov
2022-05-13  5:47 ` Martin KaFai Lau
2022-05-13 13: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=165244801337.11154.3266406533060749854.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alexei.starovoitov@gmail.com \
    --cc=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=kernel-team@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