linux-kernel - Re: [PATCH] [REVISED] net/ipv4/multipath_wrandom.c: check kmalloc() return value.

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] [day] [month] [year] [list]

Message-Id: <20070314.151151.75188950.davem@davemloft.net>
Date:	Wed, 14 Mar 2007 15:11:51 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	kiran@...lex86.org
Cc:	penberg@...helsinki.fi, amit2030@...il.com,
	linux-kernel@...r.kernel.org, akpm@...l.org,
	netdev@...r.kernel.org, shai@...lex86.org,
	pravin.shelar@...softinc.com, benzi@...lemp.com
Subject: Re: [PATCH] [REVISED] net/ipv4/multipath_wrandom.c: check
 kmalloc() return value.

From: Ravikiran G Thirumalai <kiran@...lex86.org>
Date: Wed, 14 Mar 2007 13:15:42 -0700

> The kernel bugzilla shows zaroo boogs for multipath cached as well.

Because _EVERYBODY_ turns it off because we tell them to do so!  Every
bug reported to the lists is replied to with "that code is
unbelievably buggy, just turn that off, kthx, bye".  And to reiterate
no distribution turns it on in there kernels, of course there are no
bugs reported in code nobody actually runs.

And it's been that way since day one for this code.

I also want to get rid of this code because it causes major
architectural limitations in the routing code which prevents important
work we want to do in this area.  Even the most skilled core
networking developers don't have the stomache to try and repair
what we have now, and yes they have looked at it and tried.

I'm still very much going to get rid of it, sorry.  It's unrepairable.

My deepest apologies if this inconveniences you personally, but this
is open source and you can always carry a local patch to obtain the
functionality.  In fact, it would be awesome if you took up the
project to rewrite this stuff cleanly from the start, I'd be
absolutely happy to review and integrate such patches.

But for now, what's in there has to go and there is absolutely
no question about it.
-
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/