Bug#296700: Suspect this is in 2.6.10 as well

[Micah Anderson <micah@riseup.net>]

According the upstream folks, this problem only is a problem with
kernels that have been patched with the 4G/4G patch, which is not in
the mainline.

If Debian does not use that patch, then we can close this out and
remove those patches, and I'll make a note of it in the CAN list.

Here is the thread for reference:
http://groups-beta.google.com/group/linux.kernel/browse_thread/thread/1fd2bd7a57fac50c/197ace52b8cf3b8b

Thanks,
micah

On Thu, 24 Feb 2005, Horms wrote:

> On Thu, Feb 24, 2005 at 12:43:14AM -0600, Micah Anderson wrote:
> > I looked over the 2.6.10 changelogs and do not see this being either
> > fixed, or that particular file being changed. Although I do see that it
> > has changed slightly, the piece that is replaced in this patch is not
> > replaced here. As a result, I am not able to determine myself if
> > 2.6.10 is also susceptible, but instead hope you can determine this.
> 
> I think so too, it does not seem to have been applied upstream at all.
> Do you want to ping LKML and find out if there is a reason why?
> 
> In the mean time I will go ahead and add it to 2.6.8 and 2.6.10.
> As for 2.4.27, i am not sure either. I will investigate further and
> report back.
> 
> -- 
> Horms