linux-kernel - Re: [PATCH] leave loglevel at 7 through sysrq output so you can actually read it

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]

Message-ID: <Pine.LNX.4.64.0704061903360.14457@scrub.home>
Date:	Fri, 6 Apr 2007 19:06:40 +0200 (CEST)
From:	Roman Zippel <zippel@...ux-m68k.org>
To:	Martin Bligh <mbligh@...gle.com>
cc:	Andrew Morton <akpm@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] leave loglevel at 7 through sysrq output so you can
 actually read it

Hi,

On Fri, 6 Apr 2007, Martin Bligh wrote:

> > I think you have to tell sysrq_handle_loglevel() about this too...
> 
> Not sure why? That just changes the current loglevel, and seems
> unaffected.

Who's the last to set console_loglevel?

> I did test the patch, and it works fine.

Did you check /proc/sys/kernel/printk?

bye, Roman
-
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/