From: David Miller <davem@davemloft.net>
To: kiran@scalex86.org
Cc: penberg@cs.helsinki.fi, amit2030@gmail.com,
linux-kernel@vger.kernel.org, akpm@osdl.org,
netdev@vger.kernel.org, shai@scalex86.org,
pravin.shelar@calsoftinc.com, benzi@scalemp.com
Subject: Re: [PATCH] [REVISED] net/ipv4/multipath_wrandom.c: check kmalloc() return value.
Date: Wed, 14 Mar 2007 15:11:51 -0700 (PDT) [thread overview]
Message-ID: <20070314.151151.75188950.davem@davemloft.net> (raw)
In-Reply-To: <20070314201542.GA4192@localhost.localdomain>
From: Ravikiran G Thirumalai <kiran@scalex86.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.
next prev parent reply other threads:[~2007-03-14 22:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-12 12:15 Pekka J Enberg
2007-03-12 20:56 ` David Miller
2007-03-14 20:15 ` Ravikiran G Thirumalai
2007-03-14 22:11 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-03-09 7:22 Amit Choudhary
2007-03-09 7:29 ` David Miller
2007-03-12 11:51 ` Jarek Poplawski
2007-03-12 12:36 ` Pekka Enberg
2007-03-12 13:42 ` Jarek Poplawski
2007-03-12 20:54 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070314.151151.75188950.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@osdl.org \
--cc=amit2030@gmail.com \
--cc=benzi@scalemp.com \
--cc=kiran@scalex86.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=pravin.shelar@calsoftinc.com \
--cc=shai@scalex86.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®