mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mike Waychison <mikew@google.com>
To: simon.kagstrom@netinsight.net, davem@davemloft.net
Cc: adurbin@google.com, akpm@linux-foundation.org, chavey@google.com,
	linux-kernel@vger.kernel.org, linux-api@vger.kernel.org
Subject: [PATCH v1 10/12] kmsg_dump: Export symbol kmsg_dump() to GPL modules
Date: Tue, 02 Nov 2010 18:30:25 -0700	[thread overview]
Message-ID: <20101103013024.4641.84452.stgit@crlf.mtv.corp.google.com> (raw)
In-Reply-To: <20101103012917.4641.57113.stgit@crlf.mtv.corp.google.com>

The netoops driver would like to call this function to initiate software
induced kernel dumps.

Signed-off-by: Mike Waychison <mikew@google.com>
---

This patch can go away if we have a good way to induce a 'soft' kmsg_dump in
the core kernel.
---
 kernel/printk.c |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/kernel/printk.c b/kernel/printk.c
index ad0c74e..2aa0a28 100644
--- a/kernel/printk.c
+++ b/kernel/printk.c
@@ -1572,4 +1572,5 @@ void kmsg_dump(enum kmsg_dump_reason reason, struct pt_regs *pt_regs)
 		dumper->dump(dumper, reason, pt_regs, s1, l1, s2, l2);
 	spin_unlock_irqrestore(&dump_list_lock, flags);
 }
+EXPORT_SYMBOL_GPL(kmsg_dump);
 #endif


  parent reply	other threads:[~2010-11-03  1:30 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-03  1:29 [PATCH v1 00/12] netoops support Mike Waychison
2010-11-03  1:29 ` [PATCH v1 01/12] Oops: Pass regs to oops_exit() Mike Waychison
2010-11-03  1:29 ` [PATCH v1 02/12] kmsg_dumper: Pass pt_regs along to dumpers Mike Waychison
2010-11-03  1:29 ` [PATCH v1 03/12] kmsg_dumper: Introduce a new 'SOFT' dump reason Mike Waychison
2010-11-03  1:29 ` [PATCH v1 04/12] sys-rq: Add option to soft dump Mike Waychison
2010-11-03  1:29 ` [PATCH v1 05/12] netoops: add core functionality Mike Waychison
2010-11-03  1:30 ` [PATCH v1 06/12] netoops: Add x86 specific bits to packet headers Mike Waychison
2010-11-03  1:30 ` [PATCH v1 07/12] netoops: Add user programmable fields to the netoops packet Mike Waychison
2010-11-03  1:30 ` [PATCH v1 08/12] netoops: Add one-shot mode Mike Waychison
2010-11-03  1:30 ` [PATCH v1 09/12] netoops: Add an interface to trigger various types of crashes Mike Waychison
2010-11-03  1:30 ` Mike Waychison [this message]
2010-11-03  1:30 ` [PATCH v1 11/12] ipv4: Export arp_bind_neighbour() symbol to GPL modules Mike Waychison
2010-11-03  1:30 ` [PATCH v1 12/12] netoops: Allow the driver to be built as a module Mike Waychison
2010-11-03  2:34 ` [PATCH v1 00/12] netoops support Greg KH
2010-11-03  3:37   ` Mike Waychison
2010-11-03 18:16     ` Greg KH
2010-11-03 18:50       ` Randy Dunlap
2010-11-03 19:40         ` Joe Perches
2010-11-03 20:58           ` Bruno Prémont
2010-11-03 19:03       ` Mike Waychison
2010-11-03 20:29         ` Mike Waychison
2010-11-03 20:54           ` Matt Mackall
2010-11-04  1:18             ` Mike Waychison
2010-11-04  6:35               ` Américo Wang
2010-11-04 17:38                 ` Mike Waychison
2010-11-04  6:15             ` Américo Wang
2010-11-04 17:21               ` Mike Waychison

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=20101103013024.4641.84452.stgit@crlf.mtv.corp.google.com \
    --to=mikew@google.com \
    --cc=adurbin@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=chavey@google.com \
    --cc=davem@davemloft.net \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=simon.kagstrom@netinsight.net \
    /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®