stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Kolchmeyer <rkolchmeyer@google.com>
To: stable@vger.kernel.org
Cc: Robert Kolchmeyer <rkolchmeyer@google.com>,
	Hou Tao <houtao1@huawei.com>,
	 Alexei Starovoitov <ast@kernel.org>
Subject: [PATCH v5.10 0/2] v5.10 backports for CVE-2023-52447
Date: Mon, 11 Mar 2024 17:44:33 -0700	[thread overview]
Message-ID: <cover.1710203361.git.rkolchmeyer@google.com> (raw)

Hi all,

This patch series includes backports for the changes that fix CVE-2023-52447.

The changes were applied cleanly from my 5.15 backport, viewable at
https://lore.kernel.org/stable/cover.1710187165.git.rkolchmeyer@google.com/T/#t.
The notes in that patch set largely apply here.

The only note I have for 5.10 is that the test cases with sleepable BPF
programs in commit 1624918be84a ("selftests/bpf: Add test cases for inner map")
do not seem to be compatible with the 5.10 kernel. But the situation with the
other test cases matches the observations I shared in the 5.15 patch set.

Thanks,
-Robert


Hou Tao (1):
  bpf: Defer the free of inner map when necessary

Paul E. McKenney (1):
  rcu-tasks: Provide rcu_trace_implies_rcu_gp()

 include/linux/bpf.h      |  7 ++++++-
 include/linux/rcupdate.h | 12 ++++++++++++
 kernel/bpf/map_in_map.c  | 11 ++++++++---
 kernel/bpf/syscall.c     | 26 ++++++++++++++++++++++++--
 kernel/rcu/tasks.h       |  2 ++
 5 files changed, 52 insertions(+), 6 deletions(-)

-- 
2.44.0.278.ge034bb2e1d-goog


             reply	other threads:[~2024-03-12  0:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-12  0:44 Robert Kolchmeyer [this message]
2024-03-12  0:44 ` [PATCH v5.10 1/2] rcu-tasks: Provide rcu_trace_implies_rcu_gp() Robert Kolchmeyer
2024-03-12  0:44 ` [PATCH v5.10 2/2] bpf: Defer the free of inner map when necessary Robert Kolchmeyer

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=cover.1710203361.git.rkolchmeyer@google.com \
    --to=rkolchmeyer@google.com \
    --cc=ast@kernel.org \
    --cc=houtao1@huawei.com \
    --cc=stable@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;
as well as URLs for NNTP newsgroup(s).