Am seeing a problem in mount when mounting smb file systems. There is
special code in mount for either smb or ncp where it forks to create a
child which then execs the appropriate function. The parent waits for the
child process to end. In the case of a failed smbmount, smbmount returns a
status code of 1, but the value returned to the wait is apparantly shifted
left by 8 actually returning a status code of 256 to mount. Mount
interprets the 256 as EX_BG (retry in background). When mount retries in
the background, it sends a 0 status code to the caller, which is tricked
into thinking the mount occurred successfully. This seems like a bug. Can
anyone give me an opinion or insight into the behavior of shifting the
status code by 8?
Thanks.
Mark Peloquin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun May 07 2000 - 21:00:12 EST