On Tue, Apr 05, 2011 at 11:09:33AM -0500, Tom Haynes wrote: > On Mon, Apr 04, 2011 at 11:22:31AM -0400, Bryan Schumaker wrote: > > On 04/04/2011 11:14 AM, J. Bruce Fields wrote: > > > On Mon, Apr 04, 2011 at 09:43:24AM -0400, Bryan Schumaker wrote: > > >> Hi Bruce, > > >> > > >> I'm looking at secinfo_no_name on the client. RFC 5661 says to says to send PUTROOTFH followed by SECINFO_NO_NAME in the same compound and to use SECINFO_STYLE4_CURRENT_FH. My compound is: SEQUENCE, PUTROOTFH, SECINFO_NO_NAME. The server processes up to the PUTROOTFH, and then returns with NFS4ERR_WRONGSEC. > > >> > > >> Am I doing something wrong? Is this a server problem? > > > > > > Could be; is the compound is being sent with a security flavor that > > > *isn't* permitted on the root export? > > It should never fail: > > 2.6.3.1.1.5. Put Filehandle Operation + SECINFO/SECINFO_NO_NAME > > ... > > The NFSv4.1 server MUST NOT return NFS4ERR_WRONGSEC to a put > filehandle operation that is immediately followed by SECINFO or > SECINFO_NO_NAME. The NFSv4.1 server MUST NOT return NFS4ERR_WRONGSEC > from SECINFO or SECINFO_NO_NAME. And I thought I'd implemented those recommendations at some point--I guess not! My attempt follows. --b. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
