bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: davem@davemloft.net
Cc: daniel@iogearbox.net, kuba@kernel.org, andrii@kernel.org,
	martin.lau@kernel.org, pabeni@redhat.com, edumazet@google.com,
	netdev@vger.kernel.org, bpf@vger.kernel.org, kernel-team@fb.com
Subject: pull-request: bpf 2023-01-04
Date: Wed,  4 Jan 2023 13:55:00 -0800	[thread overview]
Message-ID: <20230104215500.79435-1-alexei.starovoitov@gmail.com> (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 8 day(s) which contain
a total of 5 files changed, 112 insertions(+), 18 deletions(-).

The main changes are:

1) Always use maximal size for copy_array in the verifier to fix KASAN tracking, from Kees.

2) Fix bpf task iterator walking through dead tasks, from Kui-Feng.

3) Make sure livepatch and bpf fexit can coexist, from Chuang.

Please consider pulling these changes from:

  git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git tags/for-netdev

Thanks a lot!

Also thanks to reporters, reviewers and testers of commits in this pull-request:

Hyunwoo Kim, Jiri Olsa, Nathan Slingerland, Song Liu, Yonghong Song

----------------------------------------------------------------

The following changes since commit 40cab44b9089a41f71bbd0eff753eb91d5dafd68:

  net/sched: fix retpoline wrapper compilation on configs without tc filters (2022-12-28 12:11:32 +0000)

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 45435d8da71f9f3e6860e6e6ea9667b6ec17ec64:

  bpf: Always use maximal size for copy_array() (2022-12-28 14:54:53 -0800)

----------------------------------------------------------------
Alexei Starovoitov (2):
      selftests/bpf: Temporarily disable part of btf_dump:var_data test.
      Merge branch 'bpf: fix the crash caused by task iterators over vma'

Chuang Wang (1):
      bpf: Fix panic due to wrong pageattr of im->image

Kees Cook (1):
      bpf: Always use maximal size for copy_array()

Kui-Feng Lee (2):
      bpf: keep a reference to the mm, in case the task is dead.
      selftests/bpf: add a test for iter/task_vma for short-lived processes

 kernel/bpf/task_iter.c                            | 39 ++++++++----
 kernel/bpf/trampoline.c                           |  4 ++
 kernel/bpf/verifier.c                             | 12 ++--
 tools/testing/selftests/bpf/prog_tests/bpf_iter.c | 73 +++++++++++++++++++++++
 tools/testing/selftests/bpf/prog_tests/btf_dump.c |  2 +-
 5 files changed, 112 insertions(+), 18 deletions(-)

             reply	other threads:[~2023-01-04 21:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-04 21:55 Alexei Starovoitov [this message]
2023-01-05  4:40 ` pull-request: bpf 2023-01-04 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=20230104215500.79435-1-alexei.starovoitov@gmail.com \
    --to=alexei.starovoitov@gmail.com \
    --cc=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kernel-team@fb.com \
    --cc=kuba@kernel.org \
    --cc=martin.lau@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).