netdev - Re: 2.6.25-rc8: FTP transfer errors

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

Date:	Fri, 11 Apr 2008 18:35:37 +0400
From:	Evgeniy Polyakov <johnpol@....mipt.ru>
To:	Mark Lord <lkml@....ca>
Cc:	Ilpo Järvinen <ilpo.jarvinen@...sinki.fi>,
	David Miller <davem@...emloft.net>, jesper.juhl@...il.com,
	tilman@...p.cc, yoshfuji@...ux-ipv6.org,
	Jeff Garzik <jeff@...zik.org>, rjw@...k.pl,
	LKML <linux-kernel@...r.kernel.org>,
	Netdev <netdev@...r.kernel.org>
Subject: Re: 2.6.25-rc8: FTP transfer errors

On Fri, Apr 11, 2008 at 09:19:17AM -0400, Mark Lord (lkml@....ca) wrote:
> >>Or I can ignore it, like the net developers, since I have a workaround.
> >>And then we'll see what other apps are broken upon 2.6.25 final release.
> 
> That's not demanding, that's quite relaxed.  I had a good workaround,
> and didn't really care any more at that point.  Just though it was rather
> odd that none of the developers seemed interested in tracking it down.
> I offered tons of help, gave it, and said I didn't have time for a full
> bisect at that juncture.
> 
> For that, I get repeatedly slammed by the netdev folks.
> Even after I put aside *paid* work to submit to your demands.
> 
> Next time around, I won't bother reporting bugs to you folks,
> that's for damned sure.

Actually that will be the best decision from evolutional point of view. 

Bugs, which 'are thrown back to your face' like what you did with this
one, are useless. Developers already know, that bugs exist. 

If you do not care about bug, why do you ever bothered filling it?
You expected that anyone will start running to fix it for you.
You were wrong. Developers only fix bugs, which do not require
mind-reading and magnetic quantification of your brain.

If you do not want to help fixing it, do not expect it will be fixed at
all. Sentence, that you will probably understand better: no one get paid
to fix it.

No one get fun fixing something with description you provided
(not sure about David though, probably he has some masochistic
propensities doing that and trying to get some bits of information
from reportes for years).
You were suggested some simple checks, they did not help.
Developers can not remotely control electrons in your wires, so next
sugestion was bisecting, which ended up with some crap from your point.

If you want bug got fixed, provide info and if it is not enough, help by
trying what you are being suggested, if you do not want, stop.

-- 
	Evgeniy Polyakov
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html