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] [day] [month] [year] [list]
Date:	Tue, 28 May 2013 20:11:11 -0400
From:	Valdis.Kletnieks@...edu
To:	Christopher Sacchi <christophersacchi@...il.com>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH]: Definition for loglevel in KERN_OOPS

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?

Content of type "application/pgp-signature" skipped

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ