netdev - Re: [RFC PATCH net-2.6.24 0/5]: TCP sacktag cache usage recoded

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:	Wed, 10 Oct 2007 13:26:05 +0300 (EEST)
From:	"Ilpo Järvinen" <ilpo.jarvinen@...sinki.fi>
To:	David Miller <davem@...emloft.net>
cc:	Stephen Hemminger <shemminger@...ux-foundation.org>,
	sangtae.ha@...il.com, virtualphtn@...il.com,
	Baruch Even <baruch@...en.org>, Netdev <netdev@...r.kernel.org>
Subject: Re: [RFC PATCH net-2.6.24 0/5]: TCP sacktag cache usage recoded

On Wed, 10 Oct 2007, David Miller wrote:

> From: "Ilpo_Järvinen" <ilpo.jarvinen@...sinki.fi>
> Date: Mon, 24 Sep 2007 13:28:42 +0300
> 
> > After couple of wrong-wayed before/after()s and one infinite
> > loopy version, here's the current trial version of a sacktag  
> > cache usage recode....
> > 
> > Two first patches come from tcp-2.6 (rebased and rotated).
> > This series apply cleanly only on top of the other three patch
> > series I posted earlier today. The last debug patch provides
> > some statistics for those interested enough.
> > 
> > Dave, please DO NOT apply! ...Some thoughts could be nice
> > though :-).
> 
> Ilpo, I have not forgotten about this patch set.
> 
> It is something I plan to look over after the madness of merging
> net-2.6.24 to Linus is complete.

Thanks, there's probably going to be some trouble though, I'd bet it 
doesn't anymore apply cleanly to net-2.6.23 HEAD because of something else 
that got applied (don't remember exactly but I guess that highest_sack 
reno fix did that).

I try to get them resent soon but currently my thoughts are in solving 
DSACK ignored bug (and doing the associated cleanups) which again will 
cause those code move conflicts to reoccur. Therefore I'd love to postpone 
the rebase a bit... Hmm, SACK code is under such flux currently that I'll 
have to deal conflicts almost daily due to overlapping ideas...

-- 
 i.