[lkml]   [2009]   [Apr]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 2.6.29-git13: Reported regressions from 2.6.28

On Thu, 16 Apr 2009, Chris Friesen wrote:
> I'm okay with that. The problem causes some backwards compatibility problems
> with existing apps that get confused by the large "offset" number. The fix is
> going to cause problems too, but in a different way.
> We'll work around it.

If you have actual apps that care, that's a different issue.

We do try to bend over backwards on ABI issues if it really is noticeable
for applications. Now, in this case, if you can just fix your app to not
care (because it really was badly written in the first place to even
notice), then that is the _much_ superior solution.

But if you actually have binary-only commercial apps that break, we'll do
a compatibility thing rather than the 0 that already got merged.

Although I don't really even see what we can sanely do except for the 0
case. We could put the virtual address in there instead of zero (I forget
what old kernels used to do - whatever magic value the anonymous mappings
got, it wasn't really designed as an important value in its own right, it
was designed to trigger the "we can merge these vma's" logic.


 \ /
  Last update: 2009-04-16 23:47    [W:0.081 / U:0.920 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site