From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030630 Description of problem: Umount is called in the kernel with randon flags -- this can cause &MNT_FORCE to be true when umount was not called with '-f' See the URL for the complete bug description and patch -- but the basic information is quoted here: The problem: On IA64, the implementation of umount(2) in glibc and of sys_umount in the kernel results in the kernel performing umounts with essentially random flag words. There is a patch in the URL that fixes the problem. Version-Release number of selected component (if applicable): glibc-2.2.4-32.11 How reproducible: Always Steps to Reproduce: Reproducing this for me is seen in Lustre, trying to do a simple mount and unmount of the file system. Since unmount things MNT_FORCE is set, umount_begin() is called when not necessary. Additional info: I am not sure what more can be offered besides the patch.
Created attachment 99438 [details] A more correct patch for this version of glibc
In what way is this patch more correct than the one in CVS? I will add the INLINE_SYSCALL version.
ftp://people.redhat.com/jakub/glibc/errata/2.2.4-32.16/ should have this fixed.
*** Bug 122505 has been marked as a duplicate of this bug. ***
An errata has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2004-383.html