From: Kay Sievers <kay@vrfy.org>
To: Joe Perches <joe@perches.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: pr_cat() + CATSTR(name, size)?
Date: Wed, 11 Jul 2012 12:33:28 +0200 [thread overview]
Message-ID: <1342002808.810.12.camel@mop> (raw)
Hey Joe,
what do you think this?
It would make composing continuation lines at the caller side entirely
race-free, and it might fit into the usual pattern.
The more interesting thing, this would allow us to completely race-free
use the dev_printk() calls with continuation content, which we should
avoid otherwise for integrity reasons.
The patch below is just hacked it into the printk.c file to illustrate
the idea. It prints:
[ 0.000000] Kernel command line: root=/dev/sda2 ...
[ 0.000000] 12 34 56 78
[ 0.000000] PID hash table entries: 2048 (order: 2, 16384 bytes)
5,96,0;Kernel command line: root=/dev/sda2 ...
4,97,0;12 34 56 78
6,98,0;PID hash table entries: 2048 (order: 2, 16384 bytes)
Thanks,
Kay
diff --git a/kernel/printk.c b/kernel/printk.c
index dba1821..1fd00b0 100644
--- a/kernel/printk.c
+++ b/kernel/printk.c
@@ -48,6 +48,32 @@
#define CREATE_TRACE_POINTS
#include <trace/events/printk.h>
+#define CATSTR(name, max) \
+ char name[max]; \
+ size_t _##name_len = 0; \
+ size_t _##name_max = max;
+
+#define pr_cat(name, fmt, ...) \
+ _catstr(name, &_##name_len, _##name_max, fmt, ##__VA_ARGS__)
+
+ssize_t _catstr(char *s, size_t *len, size_t size, const char *fmt, ...)
+{
+ va_list args;
+ size_t l = *len;
+ size_t r;
+
+ va_start(args, fmt);
+ r = vsnprintf(s + l, size - l, fmt, args);
+ va_end(args);
+
+ if (r >= size - l)
+ return -EINVAL;
+
+ *len += r;
+ s[*len] = '\0';
+ return r;
+}
+
/*
* Architectures can override it:
*/
@@ -668,6 +694,12 @@ void __init setup_log_buf(int early)
char *new_log_buf;
int free;
+ CATSTR(line, 80);
+ pr_cat(line, "%i ", 12);
+ pr_cat(line, "%i ", 34);
+ pr_cat(line, "%i ", 56);
+ pr_warn("%s%i\n", line, 78);
+
if (!new_log_buf_len)
return;
next reply other threads:[~2012-07-11 10:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-11 10:33 Kay Sievers [this message]
2012-07-11 11:38 ` pr_cat() + CATSTR(name, size)? Kay Sievers
2012-07-11 15:01 ` Joe Perches
2012-07-11 15:14 ` Kay Sievers
2012-07-11 15:30 ` Joe Perches
2012-07-11 15:48 ` Kay Sievers
2012-07-11 16:55 ` Joe Perches
2012-07-11 17:25 ` Kay Sievers
2012-07-11 17:51 ` Joe Perches
2012-07-12 12:04 ` Kay Sievers
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=1342002808.810.12.camel@mop \
--to=kay@vrfy.org \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@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