a1b9ddb01d
Some paths through be_exists will set the error state, others will not There are multiple reasons that a call can fail, so clean it up a bit: all paths now return an appropriate error code so the caller can attempt to distinguish between a BE legitimately not existing and just having the wrong mountpoint. The caller is expected to bubble the error through to the internal error handler as needed. This fixes some unfriendliness with bectl(8)'s activate subcommand, where it might fail due to a bad mountpoint but the only message output is a generic "failed to activate" message. Approved by: re (gjb) |
||
|---|---|---|
| .. | ||
| be_access.c | ||
| be_error.c | ||
| be_impl.h | ||
| be_info.c | ||
| be.c | ||
| be.h | ||
| libbe.3 | ||
| Makefile | ||