Skip to content

Why the change from < to != for response decode? #14

@dcrowell77

Description

@dcrowell77

Why were all of the decoder functions changed to require exact sizes instead of "big enough" data buffers? For example from src/oem/ibm/file_io.c

if (payload_length != PLDM_RW_FILE_MEM_RESP_BYTES) {
	return PLDM_ERROR_INVALID_LENGTH;
}

This breaks some of the abstraction that we've been using because it requires the callers to explicitly understand the response structures when they didn't before.

(Note - I would normally use git blame but the "libpldm: Migrate to subproject" commit pretty much broke that without doing some bisecting so asking here.)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions