From: Peter Zijlstra <peterz@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Kees Cook <keescook@chromium.org>,
x86@kernel.org
Subject: [GIT PULL] Scope-based Resource Management for 6.5
Date: Mon, 26 Jun 2023 14:57:26 +0200 [thread overview]
Message-ID: <20230626125726.GU4253@hirez.programming.kicks-ass.net> (raw)
Hi Linus,
Please consider pulling the SBRM infrastructure so that people can start
building upon it. Specifically Greg also wants to start using this soon.
Once this lands, I'll start to trickle in the conversions I've done for
the next release.
Thanks!
---
The following changes since commit 6995e2de6891c724bfeb2db33d7b87775f913ad1:
Linux 6.4 (2023-06-25 16:29:58 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git tags/core_guards_for_6.5_rc1
for you to fetch changes up to b5ec6fd286dfa466f64cb0e56ed768092d0342ae:
kbuild: Drop -Wdeclaration-after-statement (2023-06-26 11:14:19 +0200)
----------------------------------------------------------------
Scope-based Resource Management infrastructure
These are the first few patches in the Scope-based Resource Management
series that introduce the infrastructure but not any conversions as of
yet.
Adding the infrastructure now allows multiple people to start using them.
Of note is that Sparse will need some work since it doesn't yet
understand this attribute and might have decl-after-stmt issues -- but I
think that's being worked on.
----------------------------------------------------------------
Peter Zijlstra (4):
dmaengine: ioat: Free up __cleanup() name
apparmor: Free up __cleanup() name
locking: Introduce __cleanup() based infrastructure
kbuild: Drop -Wdeclaration-after-statement
Makefile | 6 +-
arch/arm64/kernel/vdso32/Makefile | 2 -
drivers/dma/ioat/dma.c | 12 +--
include/linux/cleanup.h | 171 ++++++++++++++++++++++++++++++++++++
include/linux/compiler-clang.h | 9 ++
include/linux/compiler_attributes.h | 6 ++
include/linux/device.h | 7 ++
include/linux/file.h | 6 ++
include/linux/irqflags.h | 7 ++
include/linux/mutex.h | 4 +
include/linux/percpu.h | 4 +
include/linux/preempt.h | 5 ++
include/linux/rcupdate.h | 3 +
include/linux/rwsem.h | 8 ++
include/linux/sched/task.h | 2 +
include/linux/slab.h | 3 +
include/linux/spinlock.h | 31 +++++++
include/linux/srcu.h | 5 ++
scripts/checkpatch.pl | 2 +-
security/apparmor/include/lib.h | 6 +-
20 files changed, 282 insertions(+), 17 deletions(-)
create mode 100644 include/linux/cleanup.h
next reply other threads:[~2023-06-26 12:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 12:57 Peter Zijlstra [this message]
2023-07-04 21:11 ` Linus Torvalds
2023-07-05 7:51 ` Greg Kroah-Hartman
2023-07-04 21:12 ` pr-tracker-bot
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=20230626125726.GU4253@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=x86@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
all inboxes | Powered by JetHome®