> When the kernel tries to map these with a combined allocation, it asks > for a giant mmap of the file, but the file is, of course, not at all > that large, and the mapping is rejected. > So... I'm trying to think about how best to deal with this. If I or > anyone else can't think of an elegant solution, I'll send a revert for > the offending patch next week. Shouldn't we just be able to patch total_mapping_size() again to instead sum up all p_memsz fields, instead of comparing minimum and maximum p_vaddr? Runtime complexity would be the same as we are iterating through all segments already anyway. And I would also argue that is the behaviour that one wanted to see in that function anyway. If you agree with this, I can post a patch, but I would need to know what tree to base it on to avoid merge conflicts with the just merged patch from Alexey. -- Magnus
