You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm interested in using this library to autogen bindings for the NFS protocol (https://tools.ietf.org/html/rfc5662). Unfortunately, the spec has revealed several parsing issues.
In no particular order:
Unsigned 64-bit (hyper) integers are parsed as signed hyper integers
NFS4_UINT_MAX = 0xffffffffffffffff;
Empty structs throw a parsing error:
struct mode_masked64 {
};
thread 'main' panicked at 'Could not xdrgen lib/nfs41.x: Error(Msg("parse error: Eof: struct mode_masked64 {\n\n};\n"), State { next_error: None, backtrace: None })', libcore/result.rs:945:5
thread 'main' panicked at 'Could not xdrgen lib/nfs41.x: Error(Msg("incompat selector Named(\"status\", Ident(\"nfsstat4\", None)) case Ident(\"NFS4_OK\")")
I stopped here, but you get the idea. I'm not sure how much of this is due to a bad spec and how much of this is due to parsing difficulties, but considering these examples are from the canonical RFC laying out the XDR protocol for NFSv4 I have to assume it's probably correct.
The text was updated successfully, but these errors were encountered:
SriRamanujam
changed the title
Unsigned hyper integers are parsed as signed hyper integers
NFS XDR spec does not parse properly
Apr 23, 2018
I'm interested in using this library to autogen bindings for the NFS protocol (https://tools.ietf.org/html/rfc5662). Unfortunately, the spec has revealed several parsing issues.
In no particular order:
I stopped here, but you get the idea. I'm not sure how much of this is due to a bad spec and how much of this is due to parsing difficulties, but considering these examples are from the canonical RFC laying out the XDR protocol for NFSv4 I have to assume it's probably correct.
The text was updated successfully, but these errors were encountered: