Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
steam-runtime-tools
Manage
Activity
Members
Labels
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Analyze
Contributor analytics
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
steamrt
steam-runtime-tools
Commits
39a6a026
Commit
39a6a026
authored
5 years ago
by
Simon McVittie
Browse files
Options
Downloads
Patches
Plain Diff
v0.20200108.0
Signed-off-by:
Simon McVittie
<
smcv@collabora.com
>
parent
e460180f
Branches
Branches containing commit
Tags
pressure-vessel-v0.20200108.0
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
debian/changelog
+22
-0
22 additions, 0 deletions
debian/changelog
with
22 additions
and
0 deletions
debian/changelog
+
22
−
0
View file @
39a6a026
pressure-vessel (0.20200108.0-0+steamrt1.1) scout; urgency=medium
* wrap: Don't pass --lock-file to bwrap.
This is redundant with us passing the fd to be held by
pressure-vessel-with-lock, and it causes bwrap to produce the wrong
exit status (see https://github.com/containers/bubblewrap/issues/336
and https://github.com/containers/bubblewrap/pull/325).
* bwrap-lock: Add support for OFD locks.
On Linux >= 3.15, this allows us to pass a lock fd to a child process
across bwrap's fork-and-exec the way we were already trying to, and
have it actually work.
* wrap: Tell child process to take out its own lock if necessary.
Non-OFD locks don't propagate across fork(), and bwrap needs to clone()
itself (which behaves like fork() in this respect) to separate itself
into a parent outside the container and a child inside the container.
This change adds a weak dependency on Linux 3.15. If we run on an older
version, everything should still *work*, but there will be a short
period of time during which we have already decided to use the runtime,
but it is not locked (and in particular not protected from deletion).
-- Simon McVittie <smcv@collabora.com> Wed, 08 Jan 2020 15:34:14 +0000
pressure-vessel (0.20191216.0-0+steamrt1.1) scout; urgency=medium
pressure-vessel (0.20191216.0-0+steamrt1.1) scout; urgency=medium
* wrap: Mount pressure-vessel on /run/pressure-vessel if using runtime.
* wrap: Mount pressure-vessel on /run/pressure-vessel if using runtime.
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment