Oracle confirmed 'Bug 7161825 : acl() syscall can set errno to -1 rather than a valid error code'. It is fixed in Solaris 11(s11u1_17). Developers from Oracle are working on backporting fix to Solaris 10 right now. >From oficial description of bug correct errno code should be EFAULT.
-----Original Message----- From: Jim Meyering [mailto:[email protected]] Sent: Monday, October 08, 2012 7:45 PM To: Eric Blake Cc: Ryba, Lukas; 'Paul Eggert'; [email protected] Subject: Re: bug#12523: Solaris 10 "cp -p" returns unknown error on NFSv4 share, permissions preserve not work Eric Blake wrote: > On 10/08/2012 05:45 AM, Ryba, Lukas wrote: >> Vendor currently investigated that problem happens with the >> combination of ZFS filesystem on NFSv3 only server and NFSv3 client. >> >> 1. facl with combination of ZFS filesystem(NFSv4 acls) exported by >> NFSv4 server is ok >> 2. facl with combination of UFS filesystem(POSIX acls) exported by >> NFSv3 server is ok >> 3. facl with combination of ZFS filesystem(NFSv4 acls) exported by >> NFSv3 server fails on client with errno -1 which is our case >> IMHO errno value in case 3 should be something useful. Like ENOTSUP. > > I wonder if gnulib should write rpl_facl() that checks for the case of > facl() failing with errno set to -1 and explicitly reset errno to > ENOTSUP in that case, to work around this vendor bug. Sounds good to me, especially if the reporter confirms the fix. The added overhead of a wrapper and test-upon-failure should be acceptable for a function like facl. >> -----Original Message----- >> From: Paul Eggert [mailto:[email protected]] >> Sent: Thursday, October 04, 2012 5:53 PM >> To: Ryba, Lukas >> Cc: [email protected] >> Subject: Re: bug#12523: Solaris 10 "cp -p" returns unknown error on >> NFSv4 share, permissions preserve not work >> >> On 10/04/2012 02:19 AM, Ryba, Lukas wrote: >>> Workaround is simple. Just not use facl call right now. acl works ok. >> >> That might work around the problem on your Solaris implementation, >> but it introduces other issues, on other platforms, so I'd like >> to get at the bottom of why such a change is really needed.
