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: <4616765C.3050509@google.com>
Date:	Fri, 06 Apr 2007 09:33:32 -0700
From:	Martin Bligh <mbligh@...gle.com>
To:	Roman Zippel <zippel@...ux-m68k.org>
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

Roman Zippel wrote:
> 
> On Thu, 5 Apr 2007, Martin Bligh wrote:
> 
>> We carefully set loglevel to 7, and print the sysrq messsage
>> as to what event we're doing, but we can't actually see
>> the output as it sets it back before calling the handler,
>> rather than after.
>>
>> Move the assignment down one line.
> 
> I think you have to tell sysrq_handle_loglevel() about this too...

Not sure why? That just changes the current loglevel, and seems
unaffected.

I did test the patch, and it works fine.

M.
-
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/