Bug#394392: Alternative msync() fix for 2.6.18?
On Tue, 26 Dec 2006, Martin Michlmayr wrote:
> * Hugh Dickins <firstname.lastname@example.org> [2006-12-26 13:12]:
> > Could you point us to a description (or testcase) showing how the
> > 2.6.18 kernel's msync() is not LSB 3.1 compliant? Fixing that might
> > well be a better direction for Debian to go with a 2.6.18 kernel,
> > than applying an ever-increasing number of backports from 2.6.19
> > and 2.6.20. But I really cannot tell at this point, because I've
> > no idea what this "msync not LSB 3.1" compliant issue is. If it's
> > something easy to fix, I'd be glad to do so.
> The first message at http://bugs.debian.org/394392 contains some
> information about it, but I'm sure Jeff Licquia (CCed) can provide
> more information if necessary.
I've given that a quick look, and I'll bet it's something very
easily and safely fixed by a much simpler patch, to mm/msync.c alone,
than by all the dirty pages rework and attendant unresolved problems.
I've got to go out with the family right now, but I'll look at it in
detail this evening, and hope to come back to you with a patch then.