| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|/
|
|
|
|
|
|
| |
This moves read-only sysroot checks upfront, so that they are not
intermixed with mount operations.
It has no immediate side-effects, but allow these check to be
independent from the rest of the mounting logic (and future changes
to it).
|
|\ |
|
| |
| |
| |
| |
| | |
This adds checks around all `snprintf` calls in order to detect
failures and gracefully abort.
|
|\ \
| |/
|/| |
|
|/
|
|
|
| |
This moves a global mutable variable to a smaller local scope,
as it is not really used outside of that.
|
|\
| |
| | |
prepare-root: make all mount operations silent
|
|/
|
|
|
|
|
| |
This adds a `MS_SILENT` flag to all `mount(2)` calls, reducing the
amount of kernel logs produced on each boot.
Those messages do not contain actionable details, and in the "mount
plus read-only remount" case they can easily become highly redundant.
|
|\
| |
| | |
tests/var-mount: tweak test setup
|
|/
|
|
|
|
|
|
| |
This reworks the var-mount destructive test in order to properly use
the datadir for the current stateroot instead of a duplicated one.
In turn, it ensures that the resulting `var.mount` after reboot is
correctly pointing to the same location which hosted `/var` on the
previous boot.
|
|\
| |
| | |
ci: Enable -fanalyzer
|
| |
| |
| |
| | |
To pacify gcc's `-fanalyzer`.
|
|/
|
|
|
|
|
|
|
| |
Followup to https://github.com/ostreedev/ostree/pull/2463
One thing I noticed here is we lost usage of `build-check.sh`
which also invokes `clang`, which doesn't speak `-fanalyzer`
and would be broken by this if we try to enable `build-check.sh`
again. But that can come later.
|
|\
| |
| | |
Attempt to update packit flow to build in COPR
|
| |
| |
| |
| |
| | |
No idea if this will really work, but at least `packit srpm`
does work now.
|
|\ \
| |/
|/| |
|
|/
|
|
|
|
| |
Various fixes there, including one for `gcc -fanalyzer`.
Update submodule: libglnx
|
|\
| |
| | |
Fix various mostly theoretical gcc `-fanalyzer` issues
|
| |
| |
| |
| |
| | |
Add some not-NULL assertions for return values from glib,
and upgrade some `g_return_if_fail` to `g_assert`.
|
| |
| |
| |
| | |
Again this one is just in theory, but let's add an assertion.
|
| |
| |
| |
| |
| |
| | |
Flagged by `gcc -fanalyzer`. I didn't study this really deeply
but I think it's not actually reachable. Anyways, let's catch
it on general principle.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In general, we're probably going to need to change most of our
`g_return_if_fail` to `g_assert`. The analyzer flags that
the function can return `NULL`, but the caller isn't prepared for
this.
In practice, let's abort.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In general, we're probably going to need to change most of our
`g_return_if_fail` to `g_assert`. The analyzer flags that
the function can return `NULL`, but the caller isn't prepared for
this.
In practice, let's abort.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In general, we're probably going to need to change most of our
`g_return_if_fail` to `g_assert`. The analyzer flags that
the function can return `NULL`, but the caller isn't prepared for
this.
In practice, let's abort.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In general, we're probably going to need to change most of our
`g_return_if_fail` to `g_assert`. The analyzer flags that
the function can return `NULL`, but the caller isn't prepared for
this.
In practice, let's abort.
|
|\ \
| |/
|/| |
repo/private: move OstreeRepoAutoTransaction to a boxed type
|
| |
| |
| |
| |
| |
| |
| | |
This defines `OstreeRepoAutoTransaction` as a boxed type, in order
to support auto-generating bindings for it.
That first requires adding internal reference-counting to it, to
allow freely copying/freeing references to a single transaction guard.
|
|\ \
| |/
|/| |
docs: Do not convert -- & --- to en/em-dash
|
|/
|
|
|
| |
'--' is frequently used for command line options and was thus
incorrectly rendered as a special en-dash symbol.
|
|\
| |
| | |
prepare-root: tweak log messages to clarify errors
|
|/
|
|
|
|
|
|
| |
This rewords errors and log messages in the functions which take care
of preparing sysroot in initramfs.
Depending on the boot flow, it is possible to reach this logic
with a sysroot mounted (unexpectedly) as read-only.
In that case, let's clearly point out the problematic mountpoint.
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
We filter out everything named `-private.h` from scanning,
which differs from the gtk-doc exclude. Eventually this will
be solved when we switch to the new gir-based docs.
Came up in https://github.com/ostreedev/ostree-rs/pull/34#discussion_r723337772
|
|\ \
| |/
|/| |
test-commit-sign.sh: Skip a unit test when running as an installed-test
|
| |
| |
| |
| | |
Signed-off-by: Simon McVittie <smcv@debian.org>
|
|\ \
| |/
|/| |
Release 2021.5
|
| | |
|
|/ |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
This is nicer than having the caller parse the commit
object, or indirect via the `OstreeRepoFile*` object of the root.
Will be used in ostree-rs-ext around tar parsing.
|
|\ \
| | |
| | | |
repo/private: allow committing/aborting through a transaction guard
|
| |/
| |
| |
| |
| |
| |
| |
| |
| | |
This enhances the auto-transaction logic, augmenting the scope of a
transaction guard.
It allows committing or aborting a transaction through its guard.
It also supports tracking the completion status of a transaction
guard, avoiding double commits/aborts, while retaining the auto-cleanup
logic.
|
|\ \
| |/
|/| |
|
|/
|
|
|
|
|
|
|
|
|
| |
https://bugzilla.redhat.com/show_bug.cgi?id=1945274 is an issue where a privileged
kubernetes daemonset is writing a socket into `/etc`. This makes ostree upgrades barf.
Now, they should clearly move it to `/run`. However, one option is for us to
just ignore it instead of erroring out. Some brief investigation shows that
e.g. `git add somesocket` is a silent no-op, which is an argument in favor of ignoring it.
Closes: https://github.com/ostreedev/ostree/issues/2446
|
|\
| |
| | |
repo: Add an API to init `OstreeSePolicy` from commit directly
|
| |
| |
| |
| |
| | |
Came up in review
https://github.com/ostreedev/ostree/pull/2447#issuecomment-931428312
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is part of `OstreeCommitModifier`, but I'm not using
that in some of the ostree-ext Rust code.
It just makes more sense as a direct policy API, where it should
have been in the first place. There's already support for
setting a policy object on a commit modifier, so that's all the
old API needs to do now.
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| | |
There's a general Unix philosophy that "silence is golden".
However, when one is explicitly invoking an error check it's nice
to see explicit success.
We already print various statistics, so ending with a happy
note has no extra cost.
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| | |
This updates to the modern glib 0.14 and paves the way for
some reverse dependency testing by using ostree-ext's code.
|