linux-kernel - Re: BUG: unable to handle kernel NULL pointer dereference at 000000000000000e (reset_prng

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: <20080715214929.GA18268@martell.zuzino.mipt.ru>
Date:	Wed, 16 Jul 2008 01:49:30 +0400
From:	Alexey Dobriyan <adobriyan@...il.com>
To:	David Miller <davem@...emloft.net>, mingo@...e.hu
Cc:	nhorman@...driver.com, simon@...e.lp0.eu,
	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
	herbert@...dor.apana.org.au
Subject: Re: BUG: unable to handle kernel NULL pointer dereference at
	000000000000000e (reset_prng_context)

On Tue, Jul 15, 2008 at 01:44:07PM -0700, David Miller wrote:
> From: Ingo Molnar <mingo@...e.hu>
> 
> > i have just triggered this crash too. Please, when you know about bootup 
> > crashes in your code send a patch to the lkml thread so that people can 
> > apply it and have a working system.
> > 
> > Note that the new crypto/prng.c driver has very bad quality:
> > 
> >   total: 45 errors, 21 warnings, 1 checks, 410 lines checked
> > 
> > It has tons of completely unacceptable code mistakes in it.
> 
> I think we should merge new drivers as aggressively as possible.

Well, I don't have strong opinion about this exact statement, but

	Ingo, COULD YOU PLEASE PERSONALLY FUCKING STOP THIS
	CHECKPATCH.PL-AS-INDICATOR HORSESHIT !

Every damn single warning in this case is about whitespace or 80 column limit.

Every damn single one!

The hacker of your calibre should know the difference between whitespace-bad code
and bug-ridden-bad code.


What are those unacceptable mistakes?

Don't read the code again, what are those mistakes?


I _very_ briefly looked at prng.c and place I find wrong it passing
"int nbytes" to get_prng_bytes(). It should be unsigned at least.

checkpatch.pl says about this? Suuuure, it does...

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