linux-kernel - Re: [PATCH] [RFC] be more verbose when probing EDD

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.0712180023310.32270@fbirervta.pbzchgretzou.qr>
Date:	Tue, 18 Dec 2007 00:25:10 +0100 (CET)
From:	Jan Engelhardt <jengelh@...putergmbh.de>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
cc:	Parag Warudkar <parag.warudkar@...il.com>, devzero@....de,
	Matt.Domsch@...l.com, hpa@...or.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] [RFC] be more verbose when probing EDD


On Dec 16 2007 20:18, Alan Cox wrote:
>
>> Why tax other people with a warning/hang etc. in printk when the
>> problem is very unlikely on their systems?
>
>I think there is sense in it if you do it subtly differently.
>
>	printk(".. if this hangs do ... \r");
>	edd_stuff();
>	printk("                          \r");
>	
>
>So that we display it, do the EDD call, then write over it with whatever
>is next that matters.

Does printk support escape sequences? The last time I tried
printk("\e[1;35m omg ponies \e[0m"); that did not went too successful.

>That way you'd only see it when it hung - and that might be worth a patch
>and test from someone.
--
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/