RE: umount2() and lchown32() system calls not exercised
"Glenn Chin" <[email protected]>
| Newsgroups | gmane.linux.lsb.test-suite |
|---|---|
| Message-ID | <[email protected]> |
lchown32() wasn't called, even through glibc. I had a kernel module installed that intercepted system calls and printed the calls to /var/log/messages. However, stat64() and lstat64() were both called. -----Original Message----- From: Wichmann, Mats D [mailto:[email protected]] Sent: Sun 7/17/2005 1:37 PM To: Glenn Chin; [email protected] Subject: RE: [Lsb-test] umount2() and lchown32() system calls not exercised None of the calls you mention are tested for explicitly, since none of them are part of the specification. it's likeley that lchown32 is called "under the covers" by a glibc interface that is tested (like chown). umount is only called by the test harness, which uses a loopback filesystem for certain test conditions, not by the testcases itself. ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Glenn Chin Sent: Friday, July 15, 2005 1:34 PM To: [email protected] Subject: [Lsb-test] umount2() and lchown32() system calls not exercised I ran the lsb-runtime-test-2.0.6-2 test suite on RedHat Enterprise Linux 3 update 5 (2.4.21-32.EL). The system calls umount2() and lchown32() were never called. I know that umount() and chown32() were called. Is this known and intentional? Glenn gchin at trigence dot com _______________________________________________ lsb-test mailing list [email protected] http://mail.freestandards.org/mailman/listinfo/lsb-test