Dear all,
Some additional information if anyone else is experiencing the problem I
have described.
This problem is linked to the locking of memory before doing the
mapping.
RetCode = mlockall(MCL_FUTURE);
Causes the mmap call to fail if the mmaped file is on an ADVFS disk,
removing the call or using a 4.2BSD file system removes the problem. (it
doesn't work on either our 3000/600 or AlphaServer 1000A/266)
I have a short example program if anyone wishes to re-create/test the
problem.
-----Original Message-----
From: Walker Steve
Sent: 20 May 1998 13:58
To: alpha-osf-managers_at_ornl.gov
Subject: Bug in Patch Kit#1 for UNIX4.0D (ADVFS and mmap)
Dear All,
Has any one else experienced the following problem;
On applying patch kit #1 for Unix 4.0D our processes which use memory
mapping via mmap call do not work any more if the mapped disk file is on
an ADVFS disk. The process locks up and becomes un-interruptable in the
mmap() call i.e. 'ps' gives a U status and the process name appears in
[]. We have traced this to patch kit 1 - everything works correctly if
it is removed or the target disk is a standard BSD file system - so
beware. I will be raising a call later on today to investigate further
Steve Walker
Senior Analyst
IBM Global Services, Farnborough
Tel 01252-805389
Email: swalker_at_dsl.uk.ibm.com
Received on Tue May 26 1998 - 12:44:50 NZST