Quoting Chris Wright <[email protected]>:
* Paulo Marques ([email protected]) wrote:
This is probably a known problem that is already fixed in 2.6.14 :(
Yes, given the workaround it hasn't made priority for -stable.
There is a smaller workaround that is just to increase the number of symbols
used to make the compression by changing the "#define WORKING_SET".
This should
be just a one liner.
The downside of the workaround would be a slightly increased compile time, but
it is not *absolutely* obvious that there are no hidden consequences as is
required for the stable series.
Anyway, since this is just a compile time bug and people compiling
kernels will
probably search google when this happens and find the patch themselves,
I don't
think that it is serious enough for -stable, and we might as well hold on a
little more till 2.6.14 is out.
--
Paulo Marques
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
