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]

Message-ID: <20080411151821.GA32398@2ka.mipt.ru>
Date:	Fri, 11 Apr 2008 19:18:21 +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 10:59:57AM -0400, Mark Lord (lkml@....ca) wrote:
> >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.

Blah-blah-blah, you care so much, that pissed people off which suggested
you how to really help Linux. And then you returned with besiect
results. You helped, but if you just cared, you had missed first part.

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

Citations:
> So you will likely need to bisect.

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.

*Somebody* is responsible for those changes.
That particular *somebody* ought to volunteer some help here,
reducing the mountain of commits to a big handful or two.

-----

I can proceed - just reread a thread.

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

If you do not know math, binary search takes log2(N), so you
would only need to check at most around dozen commits. That's lot
of time to run 'git bisect good/bad', especially for man, who
"care about Linux".

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

I know one. It is guessing.

I will start: did you start hearing voices after 2.6.24 upgrade?
Or did you observed meteorites hitting wires between you machines?

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

Next time I will ask soothsayer, she really knows how to debug network
bug with following description: "it worked before I changed a kernel
version. you have to return my puppets back".

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