lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 24 Jan 2011 16:25:00 -0800
From:	Mike Waychison <mikew@...gle.com>
To:	Greg KH <greg@...ah.com>, torvalds@...ux-foundation.org
Cc:	San Mehat <san@...gle.com>, Aaron Durbin <adurbin@...gle.com>,
	Duncan Laurie <dlaurie@...gle.com>,
	linux-kernel@...r.kernel.org, Tim Hockin <thockin@...gle.com>
Subject: [PATCH v1 5/6] Allow prepending to the dmesg

The next patch in this series (Memory Console driver) would like to
prepend firmware messages to the kernel logs.

Instead of exposing all the nitty gritty lock details of the kernel's
printk system to the entire kernel, expose a "prepend_to_dmesg()" that
attempts to rewrite the in-memory dmesg to inject pre-kernel messages.

This function only prepends if the start of the kernel's messages are
still in the ring and there is still room for messages (without losing
the current tail of the message log).  We determine this by checking out
whether the bufer has yet been cleared (indicated by a new flag:
buffer_has_cleared), and by checking whether the buffer is less than
full (which would indicate that it had wrapped).

If there is enough room to prepend data, we simply shift the existing
log contents down and copy into the buffer the tail of the prepended
data that fits.

Signed-off-by: Mike Waychison <mikew@...gle.com>
---
 include/linux/printk.h |    5 ++++
 kernel/printk.c        |   55 +++++++++++++++++++++++++++++++++++++++++++++++-
 2 files changed, 59 insertions(+), 1 deletions(-)

diff --git a/include/linux/printk.h b/include/linux/printk.h
index ee048e7..df89965 100644
--- a/include/linux/printk.h
+++ b/include/linux/printk.h
@@ -113,6 +113,7 @@ extern int dmesg_restrict;
 extern int kptr_restrict;
 
 void log_buf_kexec_setup(void);
+void prepend_to_dmesg(const char *buffer, size_t length);
 #else
 static inline __attribute__ ((format (printf, 1, 0)))
 int vprintk(const char *s, va_list args)
@@ -137,6 +138,10 @@ static inline bool printk_timed_ratelimit(unsigned long *caller_jiffies,
 static inline void log_buf_kexec_setup(void)
 {
 }
+
+void prepend_to_dmesg(const char *buffer, size_t length)
+{
+}
 #endif
 
 extern void dump_stack(void) __cold;
diff --git a/kernel/printk.c b/kernel/printk.c
index 53d9a9e..aa917e3 100644
--- a/kernel/printk.c
+++ b/kernel/printk.c
@@ -144,6 +144,9 @@ static int log_buf_len = __LOG_BUF_LEN;
 static unsigned logged_chars; /* Number of chars produced since last read+clear operation */
 static int saved_console_loglevel = -1;
 
+/* Used to determine if the buffer starts at the kernel's first messages. */
+static bool buffer_has_cleared;
+
 #ifdef CONFIG_KEXEC
 /*
  * This appends the listed symbols to /proc/vmcoreinfo
@@ -344,8 +347,10 @@ int do_syslog(int type, char __user *buf, int len, bool from_file)
 		spin_lock_irq(&logbuf_lock);
 		if (count > logged_chars)
 			count = logged_chars;
-		if (do_clear)
+		if (do_clear) {
 			logged_chars = 0;
+			buffer_has_cleared = true;
+		}
 		limit = log_end;
 		/*
 		 * __put_user() could sleep, and while we sleep
@@ -383,6 +388,7 @@ int do_syslog(int type, char __user *buf, int len, bool from_file)
 	/* Clear ring buffer */
 	case SYSLOG_ACTION_CLEAR:
 		logged_chars = 0;
+		buffer_has_cleared = 0;
 		break;
 	/* Disable logging to console */
 	case SYSLOG_ACTION_CONSOLE_OFF:
@@ -844,6 +850,53 @@ out_restore_irqs:
 EXPORT_SYMBOL(printk);
 EXPORT_SYMBOL(vprintk);
 
+void __init prepend_to_dmesg(const char *buffer, size_t length)
+{
+	size_t amount_to_copy;
+	size_t copy_start;
+	unsigned long flags;
+
+	spin_lock_irqsave(&logbuf_lock, flags);
+
+	/*
+	 * Verify that the dmesg hasn't been cleared yet.  If it has,
+	 * the prepend operation is a no-op as we no longer have the
+	 * "beginning" of the kernel boot.
+	 */
+	if (buffer_has_cleared)
+		goto out;
+
+	/* Nothing to do if there is no amount in the buffer. */
+	amount_to_copy = log_buf_len - logged_chars;
+	if (!amount_to_copy)
+		goto out;
+
+	/*
+	 * At this point, we know we are on the first fill of the ring
+	 * buffer, and as such we haven't wrapped yet.
+	 */
+
+	/*
+	 * If available space in the buffer exceeds the length of the
+	 * data being prepended, trim the amount to copy.
+	 */
+	if (amount_to_copy > length)
+		amount_to_copy = length;
+
+	copy_start = length - amount_to_copy;
+
+	/* Make room by shifting the existing contents of the buffer. */
+	memmove(&log_buf[amount_to_copy], log_buf, logged_chars);
+	log_end += amount_to_copy;
+	logged_chars += amount_to_copy;
+
+	/* Inject prepended logs */
+	memmove(log_buf, buffer + copy_start, amount_to_copy);
+
+out:
+	spin_unlock_irqrestore(&logbuf_lock, flags);
+}
+
 #else
 
 static void call_console_drivers(unsigned start, unsigned end)

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ