Skip to contentSkip to conversation

Different old_mmap behavior between 2.4.5 and 2.4.8

DISCUSSION Bao C. Ha 2 participants 3 messages Sep 11, 2001

lore
Share & tools
lore

Bao C. Ha

author
#0 lore raw

We are moving from kernel 2.4.5 to kernel 2.4.8 and above. One of our applications broke due to different behaviors of the system call old_mmap.

In kernel 2.4.5:
307 old_mmap(0x7b7f7000, 36864, PROT_READ|PROT_WRITE|PROT_EXEC,
MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7b7f7000

In kernel 2.4.8:
[pid 313] old_mmap(0x7b7f7000, 36864, PROT_READ|PROT_WRITE|PROT_EXEC,
MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7b7f8000

In 2.4.5, we request 0x7b7f7000 and get the same area back. In 2.4.8, we also request 0x7b7f7000, but we are getting a different area pointed by 0x7b7f8000.

Is this supposed to be the correct behavior? What changes make the newer kernels to return different pointers? We are running on the sh4 architecture but I think these calls come from malloc() which should be arch-independent.

Appreciate any pointers/suggestions.

Thanks.
Bao

#1 lore raw
Quoted 4 lines · Bao C. Ha

Is this supposed to be the correct behavior? What changes make the newer kernels to return different pointers? We are running on the sh4 architecture but I think these calls come from malloc() which should be arch-independent.

The result from earlier kernels is wrong. If your code requires that the same address is returned as was specified then you need to pass in the MAP_FIXED flag.

-ben

author
#2 lore raw
Quoted 9 lines · Bao C. Ha
Quoted 4 lines

Is this supposed to be the correct behavior? What changes make the newer kernels to return different pointers? We are running on the sh4 architecture but I think these calls come from malloc() which should be arch-independent.

The result from earlier kernels is wrong. If your code requires that the same address is returned as was specified then you need to pass in the MAP_FIXED flag.

Unfortunately, it is the linuxthreads code that is broken on the sh4 platform. It seems that the pointers are moved due to cache aliasing. I am trying to raise awareness that this is breaking pthreads applications on sh4-linux.

Following is the relevant segment of linuxthreads that is broken:

In function pthread_allocate_stack(), file manager.c:
.......
# ifdef _STACK_GROWS_DOWN

      new_thread = default_new_thread;
      new_thread_bottom = (char *) (new_thread + 1) - stacksize;
      map_addr = new_thread_bottom - guardsize;
      res_addr = mmap(map_addr, stacksize + guardsize,
                      PROT_READ | PROT_WRITE | PROT_EXEC,
                      MAP_PRIVATE | MAP_ANONYMOUS, -1, 0);
      if (res_addr != map_addr)
        {
          /* Bad luck, this segment is already mapped. */
          if (res_addr != MAP_FAILED)
            munmap (res_addr, stacksize + guardsize);
          return -1;
        }

.......

We resort to patching the MAP_FIXED back to linuxthreads until we get a resolution on this problem.

Thanks.
Bao