BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Martin KaFai Lau <kafai@fb.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	kuba@kernel.org, kernel-team@fb.com, netdev@vger.kernel.org
Subject: Re: [PATCH bpf-next] bpf: Fix the irq and nmi check in bpf_sk_storage for tracing usage
Date: Tue, 17 Nov 2020 01:00:04 +0000	[thread overview]
Message-ID: <160557480494.19963.4345087543810572466.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201116200113.2868539-1-kafai@fb.com>

Hello:

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

On Mon, 16 Nov 2020 12:01:13 -0800 you wrote:
> The intention of the current check is to avoid using bpf_sk_storage
> in irq and nmi.  Jakub pointed out that the current check cannot
> do that.  For example, in_serving_softirq() returns true
> if the softirq handling is interrupted by hard irq.
> 
> Fixes: 8e4597c627fb ("bpf: Allow using bpf_sk_storage in FENTRY/FEXIT/RAW_TP")
> Suggested-by: Jakub Kicinski <kuba@kernel.org>
> Signed-off-by: Martin KaFai Lau <kafai@fb.com>
> 
> [...]

Here is the summary with links:
  - [bpf-next] bpf: Fix the irq and nmi check in bpf_sk_storage for tracing usage
    https://git.kernel.org/bpf/bpf-next/c/b93ef089d35c

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



      reply	other threads:[~2020-11-17  1:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-16 20:01 [PATCH bpf-next] bpf: Fix the irq and nmi check in bpf_sk_storage for tracing usage Martin KaFai Lau
2020-11-17  1:00 ` 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=160557480494.19963.4345087543810572466.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=kafai@fb.com \
    --cc=kernel-team@fb.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    /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