Re: [PATCH] fs: Restore files_lock and set_fs_root exports

[Christoph Hellwig]

On Fri, Jan 07, 2005 at 02:00:34PM -0800, Andrew Morton wrote:
> No, I'd say that unexports are different.  They can clearly break existing
> code and so should only be undertaken with caution, and with lengthy notice
> if possible.

As mentioned before we only unexported symbols were we were pretty clear
that all users of it are indeep utterly broken.  I got about a dozend
replies for this patches, and for more than half of it where the reporter
was either the author or the module was opensource I could help them to
actually fix their code.  In this case the code is far more broken than
the others, but we've even been trying to help them fix their code for
more than a year, but IBM folks have been constanly refusing.

> The cost to us of maintaining those two lines of code for a year is
> basically zero.

But as long as IBM people don't fix their %$^%! they'll continue annoying
us and the Distibutors about adding more and more hacks for it, and other
people will write similarly crappy code using it again and making the
removal even more difficult. 

> > <sarcasm>
> > <osdl-salespitch>
> > Unfortunately you don't have the financial and political powers IBM
> > has, so your opinion doesn't matter as much.  Maybe you should become
> > OSDL member to influence the direction of Linux development.
> > </osdl-salespitch>
> > </sarcasm>
> 
> Christoph, it would be better to constraint yourself to commenting on other
> people's actions rather than entering into premature speculation regarding
> their motivations, especially when that speculation involves accusations of
> corruption.

Hey, you got messages in this thread from half a dozen kernel contributors
here and still stand against all of them and for IBM who's violating our
copyrights that don't allow non-propritary derived works from it which
any user of these deeply-internal modules clearly is.

I don't know nor care nor want to speculate over anyones motives, but the
situation is at least strange enough to deserve a little sarcastic anekdote.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/