> On Mon, 12 Mar 2007 13:53:11 -0700 (PDT) David Miller <[EMAIL PROTECTED]> > wrote: > From: Jarek Poplawski <[EMAIL PROTECTED]> > Date: Mon, 12 Mar 2007 12:51:37 +0100 > > > But until then it'll unnecessarily spoil linux opinion as regards > > stability and waste time of developers to check error messages. > > So, maybe it's less evil to check those NULLs where possible and add > > some WARN_ONs here and there... > > It's a crash either way, so zero improvement. > > And _THIS_ is my big problem with the multi-path cached code in the > kernel. > > NOBODY wants to step up and fix the code, but people refuse to let it > get removed from the tree. That is totally unacceptable, so I'm going > to FIX THIS. > > I'm going to FIX IT by saying that if nobody steps up to the plate to > fix the multipath cached code by 2.6.23 IT IS GONE forver. > > And there is absolutely no negotiations about this, I've held back on > this for nearly 2 years, and nothing has happened, this code is not > maintained, nobody cares enough to fix the bugs, and even no > distributions enable it because it causes crashes.
Good stuff. I suggest you put a big printk explaining the above into 2.6.21. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
