J. Bruce Fields 4796f45740 knfsd: nfsd4: secinfo handling without secinfo= option ...

We could return some sort of error in the case where someone asks for secinfo
on an export without the secinfo= option set--that'd be no worse than what
we've been doing.  But it's not really correct.  So, hack up an approximate
secinfo response in that case--it may not be complete, but it'll tell the
client at least one acceptable security flavor.

Signed-off-by: "J. Bruce Fields" <[email protected]>
Signed-off-by: Neil Brown <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>

2007-07-17 10:23:08 -07:00

..

auth_gss.h

…

auth.h

…

cache.h

…

clnt.h

…

debug.h

…

gss_api.h

…

gss_asn1.h

…

gss_err.h

…

gss_krb5.h

…

gss_spkm3.h

…

Kbuild

…

metrics.h

…

msg_prot.h

…

rpc_pipe_fs.h

…

sched.h

…

stats.h

…

svc.h

…

svcauth_gss.h

knfsd: nfsd4: secinfo handling without secinfo= option

2007-07-17 10:23:08 -07:00

svcauth.h

…

svcsock.h

…

timer.h

…

types.h

…

xdr.h

…

xprt.h

…