Hi all,
Empty variable never exists in nvram per spec. Userspace doesn't need an
extra
EIO to figure out this known fact. In the meantime, user would wonder if
something else has gone wrong? Returning zero for reading an empty file can
reserve EIO for something more informational.
Perhaps it's not unreasonable to expect users to understand that
zero-length files don't have a corresponding EFI variable, and that the
file won't persist across a reboot.
Jeremy, thoughts?
I think that EOF would be better; it's not really an "error" condition,
just that no data has been given yet.
I'd be happy to change this check to suit.
Cheers,
Jeremy
--
To unsubscribe from this list: send the line "unsubscribe linux-efi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
