Never mind: with MAP_SHARED, the ia64 linux kernel will try to align the mapping to a 1MB boundary to avoid potentially bad performance due to false sharing, so the kernel is doing the Right Thing and it's the app that should have used MAP_PRIVATE instead. --david On 8/9/07, David Mosberger-Tang <dmosberger@xxxxxxxxx> wrote: > There is a libunwind test-case that used to work fine but fails with > recent kernels (e.g., 2.6.23-rc2). The problem is exhibited by the > attached test program. It attempts to map the page right after the > register-backing-store area with a no-access page. The mmap call > succeeds, but the kernel incorrectly maps the no-access page not at > the desired location, but at the next page. If I specify MAP_FIXED, > the mmap() call succeeds, but I don't think MAP_FIXED should be > necessary here. Anybody can think of any patches that would explain > this change of behavior? > > --david > -- > Mosberger Consulting LLC, http://www.mosberger-consulting.com/ > > -- Mosberger Consulting LLC, http://www.mosberger-consulting.com/ - To unsubscribe from this list: send the line "unsubscribe linux-ia64" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|