lbmk.git/util/libreboot-utils/include, branch master

delete util/libreboot-utils (unused code)

2026-09-07T07:12:24+00:00

this was an intense audit of nvmutil that somehow evolved
into writing a new, hardened implementation of mktemp.

it all works, a few memory bugs to solve on bsd, but i don't
see the point in keeping it. mktemp is fine, and nvmutil
already works.

lbutils implemented atomic writes and integrity checking,
in a manner completely overengineered for what it was
actually doing (modifying a few bytes in 8KB GbE files)

just delete it. i'll bring it back if i ever finish the
code. i don't want to leave dead/unfinished code in the tree.

Signed-off-by: Leah Rowe

lbutils: don't use stack memory for path strings

2026-04-21T05:39:50+00:00

Signed-off-by: Leah Rowe

lbutils: remove xpledge/xunveil, just call them direct

2026-04-21T04:54:50+00:00

Signed-off-by: Leah Rowe

remove dead code

2026-04-01T19:36:05+00:00

Signed-off-by: Leah Rowe

libreboot-utils: don't loop lseek on EINTR

2026-04-01T18:17:32+00:00

not necessary.

Signed-off-by: Leah Rowe

lbutils/file: don't loop EINTR on close()

2026-04-01T16:43:43+00:00

state is undefined after EINTR. just abort universally.

Signed-off-by: Leah Rowe

lbutils/file: rename rw_file_exact

2026-04-01T15:20:12+00:00

call it rw_exact, so that it's closer to
the name rw. it matches naming more closely;
the alternative was to call rw rw_file

but read/write can handle more than just files!

Signed-off-by: Leah Rowe

libreboot-utils/file: never retry file rw on zero

2026-04-01T15:19:46+00:00

even with a timer, it's possible that on a buggy system,
we may keep writing even though the outcome is zero. if
a system comes back with zero bytes written, that is a
fatal bug and we should stop.

Signed-off-by: Leah Rowe

lbutils: remove rw on_eintr functions. just use rw

2026-04-01T13:29:39+00:00

rw is enough. i unified everything there.

next commit will remove rw_type and instead
run positional i/o depending on whether the
offset is zero. i'm simplifying the API a lot.

Signed-off-by: Leah Rowe

lbutils: don't set USE_OPENAT and USE_URANDOM

2026-04-01T11:30:55+00:00

these can be set explicitly in the compiler flags,
e.g.

make CC="cc -DUSE_OPENAT=1 -DUSE_URANDOM=1"

these options, if set to 1, will cause you to use
the code as if it were running on non-linux systems
such as openbsd. of course, some differences will
still exist, but this is useful for portability
testing when compiling on linux.

Signed-off-by: Leah Rowe