linux-kernel - printk: fix loglevels as used by x86 stack dump code

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-next>] [day] [month] [year] [list]

Date:	Wed,  7 Oct 2009 09:39:40 +0100
From:	Alan Jenkins <alan-jenkins@...fmail.co.uk>
To:	mingo@...hat.com
Cc:	x86@...nel.org, linux-kernel@...r.kernel.org,
	torvalds@...ux-foundation.org
Subject: printk: fix loglevels as used by x86 stack dump code

Following commit 5fd29d6 "printk: clean up handling of log-levels and newlines",
I noticed some loglevel oddities in my crash logs -

 Stack:
  00000020 dbe23e7c dbe23f8c c01a62bd 00000001 d759c400 dbc61840 00000000
  <0> 08088728 08088750 00000000 dbe23e74 dbe23ea4 00000000 00000000 00000000
  <0> dbe23c18 00c7afc0 c01a6eb1 ffffffff 00000000 dbc61840 00000000 00000000


This series is the result of my investigation.  The main fixes are

[PATCH 6/7] x86 dumpstack: fix printing of stack dump loglevels
 - fixes the problem shown above

[PATCH 5/7] printk: fix printk(KERN_EMERG) followed by printk("emergency message\n")
 - make sure the call trace which follows the stack dump is logged as KERN_EMERG,
   and not KERN_DEFAULT.

Regards
Alan
--
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/