From: Martin KaFai Lau <martin.lau@linux.dev>
To: davem@davemloft.net
Cc: kuba@kernel.org, edumazet@google.com, pabeni@redhat.com,
daniel@iogearbox.net, andrii@kernel.org, ast@kernel.org,
netdev@vger.kernel.org, bpf@vger.kernel.org
Subject: pull-request: bpf 2023-08-03
Date: Thu, 3 Aug 2023 11:14:29 -0700 [thread overview]
Message-ID: <20230803181429.994607-1-martin.lau@linux.dev> (raw)
Hi David, hi Jakub, hi Paolo, hi Eric,
The following pull-request contains BPF updates for your *net* tree.
We've added 5 non-merge commits during the last 7 day(s) which contain
a total of 3 files changed, 37 insertions(+), 20 deletions(-).
The main changes are:
1) Disable preemption in perf_event_output helpers code from Jiri Olsa
2) Add length check for SK_DIAG_BPF_STORAGE_REQ_MAP_FD parsing from Lin Ma
3) Multiple warning splat fixes in cpumap from Hou Tao
Thanks a lot!
Also thanks to reporters, reviewers and testers of commits in this pull-request:
Hou Tao, Jakub Kicinski, Jesper Dangaard Brouer, Oleg Popov, Pu Lehui
----------------------------------------------------------------
The following changes since commit 284779dbf4e98753458708783af8c35630674a21:
net: stmmac: Apply redundant write work around on 4.xx too (2023-07-25 11:03:55 +0200)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git tags/for-netdev
for you to fetch changes up to 4c9fbff54297471d4e2bbfe9c27e80067c722eae:
Merge branch 'Two fixes for cpu-map' (2023-07-31 15:45:38 -0700)
----------------------------------------------------------------
pull-request: bpf 2023-08-03
----------------------------------------------------------------
Alexei Starovoitov (1):
Merge branch 'bpf-disable-preemption-in-perf_event_output-helpers-code'
Hou Tao (2):
bpf, cpumap: Make sure kthread is running before map update returns
bpf, cpumap: Handle skb as well when clean up ptr_ring
Jiri Olsa (2):
bpf: Disable preemption in bpf_perf_event_output
bpf: Disable preemption in bpf_event_output
Lin Ma (1):
bpf: Add length check for SK_DIAG_BPF_STORAGE_REQ_MAP_FD parsing
Martin KaFai Lau (1):
Merge branch 'Two fixes for cpu-map'
kernel/bpf/cpumap.c | 35 +++++++++++++++++++++--------------
kernel/trace/bpf_trace.c | 17 ++++++++++++-----
net/core/bpf_sk_storage.c | 5 ++++-
3 files changed, 37 insertions(+), 20 deletions(-)
next reply other threads:[~2023-08-03 18:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 18:14 Martin KaFai Lau [this message]
2023-08-03 22:11 ` pull-request: bpf 2023-08-03 patchwork-bot+netdevbpf
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=20230803181429.994607-1-martin.lau@linux.dev \
--to=martin.lau@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).