[Bugs] [Bug 1336889] Gluster's XDR does not conform to RFC spec

bugzilla at redhat.com bugzilla at redhat.com
Tue Oct 24 14:00:53 UTC 2017


https://bugzilla.redhat.com/show_bug.cgi?id=1336889

Amar Tumballi <atumball at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|unspecified                 |medium
             Status|NEW                         |ASSIGNED
                 CC|                            |atumball at redhat.com
           Assignee|mchangir at redhat.com         |atumball at redhat.com



--- Comment #4 from Amar Tumballi <atumball at redhat.com> ---
Planning to not resolve below:

>> 2. "unsigned char" is also not defined. Its uses in the form "unsigned char uuid[16]" are almost certainly not what was intended; this will serialize as an array of 16 bytes padded to 32 bits, generating 16x4=64 bytes on the wire. The correct form is "opaque uuid[16]", but changing this will break the wire format. A compatible fix is to define a "byte" or "uchar" type and use that: "byte uuid[16]" (in Rust, this would map to "u8")

As it will cause the glusterd cluster break, which anyways is targeted to be
taken out of support by 4.1.x releases.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=4RqVxNYzMW&a=cc_unsubscribe


More information about the Bugs mailing list