From: Valdis.Kletnieks@vt.edu
To: Christopher Sacchi <christophersacchi@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH]: Definition for loglevel in KERN_OOPS
Date: Tue, 28 May 2013 20:11:11 -0400 [thread overview]
Message-ID: <4136.1369786271@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Tue, 28 May 2013 20:00:45 -0400." <CABQQNFGaS9rKaWto75fVQ5Ru+XKU2hgBRBjnV8G6WGf_TeMt9g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 713 bytes --]
On Tue, 28 May 2013 20:00:45 -0400, Christopher Sacchi said:
> This patch is for linux-3.10-rc2 and adds the definition for
> KERN_OOPS (it can be used for whenever kernel oops occur) in
> <linux/kern_loglevel.h> for <linux/printk.h>. It is below the
> double-dashes.
OK, I'll bite.
1) Where in the kernel will this actually get used?
2) Are there any matching patches for userspace tools like syslog
to make it useful?
3) Was it intenional that you added this:
+#define KERN_OOPS KERN_SOH "2" /* kernel oops condition */
instead of
+#define KERN_OOPS KERN_CRIT
4) How does a syslog daemon distringuish between KERN_CRIT and KERN_OOPS?
In other words - why do we need this patch?
[-- Attachment #2: Type: application/pgp-signature, Size: 865 bytes --]
prev parent reply other threads:[~2013-05-29 0:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-29 0:00 Christopher Sacchi
2013-05-29 0:11 ` Valdis.Kletnieks [this message]
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=4136.1369786271@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=christophersacchi@gmail.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
all inboxes | Powered by JetHome®