From: david.laight.linux@gmail.com
To: Thomas Gleixner <tglx@linutronix.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Kees Cook <kees@kernel.org>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
Al Viro <viro@zeniv.linux.org.uk>
Cc: David Laight <david.laight.linux@gmail.com>
Subject: [PATCH 2/5] compiler.h: Add generic support for 'autoterminating nested for() loops'
Date: Sat, 20 Dec 2025 21:56:05 +0000 [thread overview]
Message-ID: <20251220215608.434614-3-david.laight.linux@gmail.com> (raw)
In-Reply-To: <20251220215608.434614-1-david.laight.linux@gmail.com>
From: David Laight <david.laight.linux@gmail.com>
Autoterminating nested for() loops can be used inside #defines to
declare variables that are scoped to the statement that follows.
These are used by __scoped_user_access() but may have other uses
and the gory details are best separated from the use.
Using 'with (declaration)' and 'and_with (declaration)' seems to
read reasonably well and doesn't seem to collide with any existing
code.
As an example the scoped user access definition becomes:
with (typeof(uptr) _tmpptr = __scoped_user_access_begin(mode, uptr, size, elbl)) \
and_with (CLASS(user_##mode##_access, scope)(_tmpptr)) \
/* Force modified pointer usage within the scope */ \
and_with (const typeof(uptr) uptr = _tmpptr)
Signed-off-by: David Laight <david.laight.linux@gmail.com>
---
include/linux/compiler.h | 26 ++++++++++++++++++++++++++
1 file changed, 26 insertions(+)
diff --git a/include/linux/compiler.h b/include/linux/compiler.h
index 04487c9bd751..da89a5efda5a 100644
--- a/include/linux/compiler.h
+++ b/include/linux/compiler.h
@@ -377,6 +377,32 @@ static inline void *offset_to_ptr(const int *off)
*/
#define prevent_tail_call_optimization() mb()
+/*
+ * Sometimes a #define needs to declare a variable that is scoped
+ * to the statement that follows without having mismatched {}.
+ * with (int x = expression) {
+ * statements
+ * }
+ * is the same as:
+ * {
+ * int x = expression;
+ * statements
+ * }
+ * but lets it all be hidden from the call site, eg:
+ * frobnicate(args) {
+ * statements
+ * }
+ * Only a single variable can be defined, and_with() allows extra ones
+ * without adding an additional outer loop.
+ *
+ * The controlled scope can be terminated using break, continue or goto.
+ */
+#define with(declaration) \
+ for (bool _with_done = false; !_with_done; _with_done = true) \
+ and_with (declaration)
+#define and_with(declaration) \
+ for (declaration; !_with_done; _with_done = true)
+
#include <asm/rwonce.h>
#endif /* __LINUX_COMPILER_H */
--
2.39.5
next prev parent reply other threads:[~2025-12-20 21:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-20 21:56 [PATCH 0/5] uaccess: Updates to scoped_user_access() david.laight.linux
2025-12-20 21:56 ` [PATCH 1/5] uaccess: Fix scoped_user_read_access() for 'pointer to const' david.laight.linux
2025-12-20 21:56 ` david.laight.linux [this message]
2025-12-20 21:56 ` [PATCH 3/5] uaccess.h: Use with() and and_with() in __scoped_user_access() david.laight.linux
2025-12-20 21:56 ` [PATCH 4/5] uaccess: Disable -Wshadow " david.laight.linux
2025-12-20 21:56 ` [PATCH 5/5] signal: Use scoped_user_access() instead of __put/get_user() david.laight.linux
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=20251220215608.434614-3-david.laight.linux@gmail.com \
--to=david.laight.linux@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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®