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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 11 Apr 2008 10:59:57 -0400
From:	Mark Lord <lkml@....ca>
To:	Evgeniy Polyakov <johnpol@....mipt.ru>
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

Evgeniy Polyakov wrote:
> 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?
..

Because I care, about Linux's reputation and performance.
I care about basic networking operations, and knew that this bug
would probably affect other applications once widely deployed.

I care about Linux.  That's why.

> If you do not want to help fixing it ...

Where the hell did I *ever* say that?
I did nothing but offer help, and respond quickly.

The one thing I did not have time for initially,
was a painstaking blunt instrument binary search of
every commit since v2.6.24.

There are other ways to debug things and find the causes
quickly, with less impact upon the reporters of bugs.

The current generation of kernel "code submitters" here
seems to have never learned those.  Bummer.

Cheers
--
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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ