linux-kernel - Re: [PATCH] Stop scaring users with "treason uncloaked!"

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20081218.160746.58836056.davem@davemloft.net>
Date:	Thu, 18 Dec 2008 16:07:46 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	alan@...rguk.ukuu.org.uk
Cc:	herbert@...dor.apana.org.au, mpm@...enic.com,
	linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH] Stop scaring users with "treason uncloaked!"

From: Alan Cox <alan@...rguk.ukuu.org.uk>
Date: Thu, 18 Dec 2008 23:14:07 +0000

> On Fri, 19 Dec 2008 10:02:53 +1100
> Herbert Xu <herbert@...dor.apana.org.au> wrote:
> 
> > Well
> > 
> > $ grep fire drivers/char/lp.c
> >                         printk(KERN_INFO "lp%d on fire\n", minor);
> 
> Interesting. It got changed and then the change got lost between 2.2 and
> 2.4 somewhere. It was changed to report
> 
> "lp0 reported invalid error status (on fire, eh?)"
> 
> and it looks like that needs re-fixing.

This is just proof that it doesn't matter.  If it got lost in
2.4.x that means it's been like this forever as far as %99
of current systems are concerned.

I'm all for seriousness, but if we can't have some comedic license
with a few kernel log messages then the fun of kernel development
truly suffers :-)
--
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/