diff options
| author | Chuck Lever <cel@kernel.org> | 2026-09-16 12:28:30 -0400 |
|---|---|---|
| committer | Chuck Lever <cel@kernel.org> | 2026-10-11 23:12:10 -0400 |
| commit | 9c8a74ada92937e39a3880f0ec9206686dd280c0 (patch) | |
| tree | 8db15e0be28e6bebc3ffded4129dfd92f4437805 /rust/kernel/alloc/kvec/errors.rs | |
| parent | b1eb9f1aea88a0d7ec8116a70c33b7b31ad0a3eb (diff) | |
Documentation: Add the RPC language description of NFSv2
In order to generate source code to encode and decode NFSv2 protocol
elements, include a copy of the RPC language description of NFSv2
for xdrgen to process. The language description is an amalgam of
RFC 1094 and the Open Group's XNFS specification:
https://pubs.opengroup.org/onlinepubs/9629799/chap7.htm
The goals of replacing hand-written XDR functions with ones that
are tool-generated are to improve memory safety and make XDR
encoding and decoding less brittle to maintain. Parts of the
NFSv4 protocol are still being extended actively. Tool-generated
XDR code reduces the time it takes to get a working implementation
of new protocol elements.
The xdrgen utility derives both the type definitions and the
encode/decode functions directly from protocol specifications,
using names and symbols familiar to anyone who knows those specs.
Unlike hand-written code that can inadvertently diverge from the
specification, xdrgen guarantees that the generated code matches
the specification exactly.
We would eventually like xdrgen to generate Rust code as well,
making the conversion of the kernel's NFS stacks to use Rust just
a little easier for us.
Acked-by: Jeff Layton <jlayton@kernel.org>
Link: https://patch.msgid.link/20260916162859.2051-2-cel@kernel.org
Signed-off-by: Chuck Lever <cel@kernel.org>
Diffstat (limited to 'rust/kernel/alloc/kvec/errors.rs')
0 files changed, 0 insertions, 0 deletions
