Hi Olga- > On Mar 10, 2020, at 2:58 PM, Olga Kornievskaia <aglo@xxxxxxxxx> wrote: > > Ever since commit 2c94b8eca1a26 "SUNRPC: Use au_rslack when computing > reply buffer size". It changed how "req->rq_rcvsize" is calculated. It > used to use au_cslack value which was nice and large and changed it to > au_rslack value which turns out to be too small. > > Since 5.1, v3 mount with sec=krb5p fails against an Ontap server > because client's receive buffer it too small. Can you be more specific? For instance, why is 100 bytes adequate for Linux servers, but not OnTAP? Is this explanation for the current value not correct? 51 /* length of a krb5 verifier (48), plus data added before arguments when 52 * using integrity (two 4-byte integers): */ > For GSS, au_rslack is calculated from GSS_VERF_SLACK value which is > currently 100. And it's not enough. Changing it to 104 works and then > au_rslack is recalculated based on actual received mic.len and not > just the default buffer size. > > I would like to propose to change it to something a little larger than > 104, like 120 to give room if some other server might reply with > something even larger. Why does it need to be larger than 104? > Thoughts? Will send an actual patch if no objections to this one. > > diff --git a/net/sunrpc/auth_gss/auth_gss.c b/net/sunrpc/auth_gss/auth_gss.c > index 24ca861..44ae6bc 100644 > --- a/net/sunrpc/auth_gss/auth_gss.c > +++ b/net/sunrpc/auth_gss/auth_gss.c > @@ -50,7 +50,7 @@ > #define GSS_CRED_SLACK (RPC_MAX_AUTH_SIZE * 2) > /* length of a krb5 verifier (48), plus data added before arguments when > * using integrity (two 4-byte integers): */ > -#define GSS_VERF_SLACK 100 > +#define GSS_VERF_SLACK 120 > > static DEFINE_HASHTABLE(gss_auth_hash_table, 4); > static DEFINE_SPINLOCK(gss_auth_hash_lock); -- Chuck Lever
