Chuck Lever 35e77d21ba
SUNRPC: Add rpc_auth::au_ralign field ...
Currently rpc_inline_rcv_pages() uses au_rslack to estimate the
size of the upper layer reply header. This is fine for auth flavors
where au_verfsize == au_rslack.
However, some auth flavors have more going on. krb5i for example has
two more words after the verifier, and another blob following the
RPC message. The calculation involving au_rslack pushes the upper
layer reply header too far into the rcv_buf.
au_rslack is still valuable: it's the amount of buffer space needed
for the reply, and is used when allocating the reply buffer. We'll
keep that.
But, add a new field that can be used to properly estimate the
location of the upper layer header in each RPC reply, based on the
auth flavor in use.
Signed-off-by: Chuck Lever <chuck.lever@oracle.com >
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com >
2019-02-14 11:48:36 -05:00
2019-01-09 13:21:02 -08:00
2019-01-07 22:47:48 +01:00
2019-01-01 15:45:48 -08:00
2018-12-28 20:54:57 -08:00
2018-12-28 20:00:21 -08:00
2019-01-31 12:51:33 +00:00
2019-01-15 06:24:36 +12:00
2018-12-28 14:57:10 -08:00
2018-12-28 16:52:18 -08:00
2018-12-28 20:54:57 -08:00
2019-01-12 21:07:14 -08:00
2019-01-02 18:56:59 -08:00
2018-12-28 20:22:45 -08:00
2019-01-25 15:32:28 -08:00
2019-02-01 15:46:23 -08:00
2018-12-28 16:52:18 -08:00
2019-02-14 11:48:36 -05:00
2019-01-22 14:39:38 -07:00
2019-01-05 13:18:59 -08:00
2019-01-24 11:11:45 -07:00
2018-12-28 14:48:06 -08:00
2019-02-07 12:57:17 -07:00
2019-01-05 21:32:38 -08:00
2019-01-11 18:05:41 -08:00
2019-01-04 13:13:45 -08:00
2018-12-28 12:11:43 -08:00
2019-01-09 11:36:41 +01:00
2019-01-21 07:23:42 +13:00
2019-01-09 11:36:41 +01:00
2019-01-09 11:36:41 +01:00
2019-01-30 19:27:00 +01:00
2019-01-30 11:02:11 -08:00
2019-01-04 09:02:17 +01:00
2019-01-08 07:58:49 -05:00
2019-01-06 09:46:51 +09:00
2019-01-02 09:43:14 -08:00
2019-01-16 17:42:35 +01:00
2019-01-31 23:14:55 +01:00
2019-01-30 11:02:11 -08:00
2018-12-31 11:46:59 -08:00
2019-01-04 13:13:46 -08:00
2018-12-28 12:11:52 -08:00
2019-01-29 12:09:11 +01:00
2019-01-16 14:29:48 +01:00
2018-12-28 12:11:47 -08:00
2018-12-28 12:11:52 -08:00
2018-12-28 12:11:50 -08:00
2019-01-09 14:20:47 -05:00
2019-01-31 08:25:09 -07:00
2019-01-24 22:45:34 -08:00
2019-01-18 00:18:45 +01:00
2019-01-06 09:46:51 +09:00
2019-01-06 09:46:51 +09:00
2018-12-28 12:11:44 -08:00
2019-01-04 13:13:47 -08:00
2018-12-30 08:33:06 +00:00
2019-01-21 09:57:43 -08:00
2018-12-28 12:11:49 -08:00
2018-12-28 12:11:48 -08:00
2019-02-01 15:46:23 -08:00
2018-12-28 12:11:52 -08:00
2018-12-28 12:11:51 -08:00
2019-01-04 13:13:48 -08:00
2019-01-04 13:13:48 -08:00
2018-12-28 12:11:50 -08:00
2019-01-08 17:15:11 -08:00
2019-01-09 10:35:56 +01:00
2019-01-30 22:13:34 -08:00
2019-01-06 09:46:51 +09:00
2019-01-06 09:46:51 +09:00
2019-01-10 16:24:44 -06:00
2018-12-28 12:11:48 -08:00
2018-12-28 12:11:44 -08:00
2018-12-28 12:11:50 -08:00
2018-12-28 12:11:46 -08:00
2018-12-28 12:11:51 -08:00
2018-12-28 12:11:48 -08:00
2019-01-05 17:57:34 -08:00
2019-01-08 07:58:37 -05:00
2019-01-05 17:57:34 -08:00
2019-01-19 10:03:08 -08:00
2019-01-04 12:19:40 +01:00
2019-01-30 22:49:06 +01:00
2019-01-04 13:13:46 -08:00
2019-01-01 11:58:33 -08:00
2019-01-10 17:04:45 -06:00
2019-01-03 18:57:57 -08:00
2019-01-07 16:38:26 +01:00
2019-02-03 09:08:12 -08:00
2019-01-12 11:48:20 -06:00
2019-01-18 14:05:14 -08:00
2018-12-28 12:11:44 -08:00
2018-12-29 11:21:49 -08:00
2018-12-28 12:45:04 -08:00
2019-01-30 22:24:49 -08:00
2018-12-28 12:11:47 -08:00
2019-01-02 09:48:13 -08:00
2019-01-04 12:56:09 -08:00
2019-01-11 18:05:40 -08:00
2019-01-14 20:15:17 -05:00
2018-12-28 12:11:51 -08:00
2019-01-17 07:19:42 -05:00
2018-12-28 12:11:46 -08:00
35e77d21ba