summaryrefslogtreecommitdiffstats
path: root/net/l2tp/l2tp_netlink.c
diff options
context:
space:
mode:
authorJ. Bruce Fields <bfields@redhat.com>2012-12-03 21:50:38 +0100
committerJ. Bruce Fields <bfields@redhat.com>2012-12-04 13:49:24 +0100
commit836fbadb96a8308e6283eee5c7b3bdae818b58ca (patch)
treebeb0b70d57d7ac98adbc1931483f2c2ff5d0325f /net/l2tp/l2tp_netlink.c
parentsvcrpc: track rpc data length separately from sk_tcplen (diff)
downloadlinux-836fbadb96a8308e6283eee5c7b3bdae818b58ca.tar.xz
linux-836fbadb96a8308e6283eee5c7b3bdae818b58ca.zip
svcrpc: support multiple-fragment rpc's
Over TCP, RPC's are preceded by a single 4-byte field telling you how long the rpc is (in bytes). The spec also allows you to send an RPC in multiple such records (the high bit of the length field is used to tell you whether this is the final record). We've survived for years without supporting this because in practice the clients we care about don't use it. But the userland rpc libraries do, and every now and then an experimental client will run into this. (Most recently I noticed it while trying to write a pynfs check.) And we're really on the wrong side of the spec here--let's fix this. Signed-off-by: J. Bruce Fields <bfields@redhat.com>
Diffstat (limited to 'net/l2tp/l2tp_netlink.c')
0 files changed, 0 insertions, 0 deletions