Re: FIXED (was Re: PROBLEM: Blk Dev Cache causing kswapd thrashing)

From: Chris Petersen
Date: Wed Dec 10 2003 - 14:05:37 EST


Dave Jones wrote:
>
> On Wed, Dec 10, 2003 at 12:44:42PM -0500, Chris Petersen wrote:
> >
> > To confuse matters RedHat has released an RPM with 2.4.20-24.7 which
> > apparently contains later patches that include the fix.
>
> 2.4.20-24.7 contains two patches. Both security issues. (do_brk
> and an nptl local DoS), nothing else (vs previous 2.4.20-20.7)

I wasn't claiming that it wasn't fixed UNTIL 2.4.20-24.7 specifically.
I was merely stating that 2.4.20-24.7 appears to contain the fix.

After some research it looks like the fix is sortof there in
RedHat's 2.4.20-13.7. It behaves better, but not as good as 2.4.23
or 2.4.20-24.7. By "better" I mean kswapd (and bdflush, kupdated,
kreclaimd) doesn't hog the CPU(s) as much; but it still does to
a greater extent compared to what I'm calling the "fixed" versions.
So in 2.4.20-13.7 it's quasi-busted or quasi-fixed, depending on
your half-full/empty position.

> > This can be
> > confusing because their 2.4.21-4EL kernel is busted (WRT this bug)
>
> That kernel bears no relation whatsoever to 2.4.20-24.7
> It's for a completely different product for one thing, with
> very little in common between them (in terms of patches we add).

Exactly my point!

I suppose I am working from the assumption that if vanilla
(kernel.org) 2.4.20 was fixed then 2.4.21-4EL would also be fixed
(which it's not). It would seem to me that a kernel's got no
business calling itself 2.4.21-<anything> if it's not based off of
previous kernel base. Otherwise, "21" has absolutely no meaning.

Imperical evidence seems to indicate that vanilla 2.4.20 does not
contain the fix. Whereas something that RedHat calls 2.4.20-XYZ does.

-chris

-----------------------------------------------------------------
Chris M. Petersen cmp@xxxxxxxxxxxx
Sr. R&D Engineer

Synopsys, Inc. o: 919.425.7342
1101 Slater Road, Suite 300 c: 919.349.6393
Durham, NC 27703 f: 919.425.7320
-----------------------------------------------------------------
-
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/