Leah Rowe 257eedca0c util/nvmutil: reset errno if any write attempted ...

the way nvmutil is designed, setWord() is only ever called
under non-error conditions. however, if one part is valid but
the other one isn't, and a command is run that touches both parts,
errno is non-zero write writeGbeFile is called

in situations where one part is valid, but the other isn't, AND the
writes to gbe (in memory) results in a non-change, writeGbeFile is
not called; in this situation, errno is not being reset, despite
non-error condition

this patch fixed the bug, resulting in zero status upon exit under
such conditions

2023-01-28 22:14:35 +00:00

..

nvmutil

util/nvmutil: reset errno if any write attempted

2023-01-28 22:14:35 +00:00