This bug was fixed in the package systemd - 229-4ubuntu21.17
---
systemd (229-4ubuntu21.17) xenial; urgency=medium
[ Victor Tapia ]
* d/p/stop-mount-error-propagation.patch:
keep mount errors local to the failing mount point instead of blocking
the processing of all
** Changed in: systemd (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795764
Title:
systemd: core: Fix edge case when processing /proc/self/mountinfo
To
for autopkgtest regression failure justifications, see bug 1755863
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795764
Title:
systemd: core: Fix edge case when processing /proc/self/mountinfo
To
oops, @slashd already verified :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795764
Title:
systemd: core: Fix edge case when processing /proc/self/mountinfo
To manage notifications about this
root@systemd-x:/tmp# dpkg -l | grep libsystemd0
ii libsystemd0:amd64229-4ubuntu21.16
amd64systemd utility library
root@systemd-x:/tmp# mkdir -p bind-test/abc
root@systemd-x:/tmp# mount --bind bind-test bind-test
root@systemd-x:/tmp# mount -t
[VERIFICATION XENIAL]
Using the protocol mentioned in the [Test Case] with systemd from
xenial-proposed, version : 229-4ubuntu21.17. I can no longer reproduce
the situation.
# systemctl list-units --all | grep bind-test
mnt-bind\x2dtest.mount loadedactive mounted
Hello Joshua, or anyone else affected,
Accepted systemd into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21.17 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Changed in: systemd (Ubuntu Xenial)
Assignee: Dimitri John Ledkov (xnox) => Eric Desrochers (slashd)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795764
Title:
systemd: core: Fix edge
** Changed in: systemd (Ubuntu Xenial)
Assignee: Eric Desrochers (slashd) => Dimitri John Ledkov (xnox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795764
Title:
systemd: core: Fix edge
A security fix has superseded the current SRU. The SRU will need to be
restarted from scratch.
debian/changelog
--
systemd (229-4ubuntu21.15) xenial-security; urgency=medium
* SECURITY UPDATE: memory corruption in journald via attacker controlled alloca
- debian/patches/CVE-2018-16864.patch:
Hi Joshua,
Have you been able to test the systemd proposed package using your k8s
setup reproducer ?
I'll be curious to hear about the outcome before I request the release
of this package to its final destination: xenial-updates and mark the
end of this particular SRU.
Regards,
Eric
--
You
** Description changed:
[Impact]
kubernetes loaded inactive dead transient mount points grows
https://github.com/kubernetes/kubernetes/issues/57345
[Test Case]
# cd /tmp
# mkdir -p bind-test/abc
# mount --bind bind-test bind-test
# mount -t tmpfs tmpfs bind-test/abc
#
I tested the systemd 229-4ubuntu21.11 package from xenial-proposed in
Ubuntu 16.04 in KVM and also confirm I cannot reproduce the issue with
this updated package:
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.5 LTS
Release:16.04
[VERIFICATION XENIAL]
I confirm that this specific bug is now fix with that proposed package.
# Confirmation of the use of proposed systemd packages:
ii libpam-systemd:amd64229-4ubuntu21.11
amd64system and service manager - PAM module
ii
** Description changed:
[Impact]
kubernetes loaded inactive dead transient mount points grows
https://github.com/kubernetes/kubernetes/issues/57345
[Test Case]
# cd /tmp
# mkdir -p bind-test/abc
# mount --bind bind-test bind-test
# mount -t tmpfs tmpfs bind-test/abc
#
Regression in autopkgtest for nplan (amd64): test log
It's failling in the Ubuntu infra but passing when ran manually in my
own HW, here's the full output in attachment: autopkgtest_result.txt
- Eric
** Description changed:
[Impact]
kubernetes loaded inactive dead transient mount
Regression in autopkgtest for nplan (amd64): test log
It's failling in the Ubuntu infra but passing when ran manually in my
own HW, here's the full output in attachment: autopkgtest_result.txt
- Eric
** Attachment added: "autopkgtest_result.txt"
** Description changed:
[Impact]
kubernetes loaded inactive dead transient mount points grows
https://github.com/kubernetes/kubernetes/issues/57345
[Test Case]
# cd /tmp
# mkdir -p bind-test/abc
# mount --bind bind-test bind-test
# mount -t tmpfs tmpfs bind-test/abc
#
** Description changed:
[Impact]
kubernetes loaded inactive dead transient mount points grows
https://github.com/kubernetes/kubernetes/issues/57345
[Test Case]
# cd /tmp
# mkdir -p bind-test/abc
# mount --bind bind-test bind-test
# mount -t tmpfs tmpfs bind-test/abc
#
** Description changed:
[Impact]
kubernetes loaded inactive dead transient mount points grows
https://github.com/kubernetes/kubernetes/issues/57345
[Test Case]
# cd /tmp
# mkdir -p bind-test/abc
# mount --bind bind-test bind-test
# mount -t tmpfs tmpfs bind-test/abc
#
** Description changed:
[Impact]
kubernetes loaded inactive dead transient mount points grows
https://github.com/kubernetes/kubernetes/issues/57345
[Test Case]
# cd /tmp
# mkdir -p bind-test/abc
# mount --bind bind-test bind-test
# mount -t tmpfs tmpfs bind-test/abc
#
** Description changed:
[Impact]
kubernetes loaded inactive dead transient mount points grows
https://github.com/kubernetes/kubernetes/issues/57345
[Test Case]
# cd /tmp
# mkdir -p bind-test/abc
# mount --bind bind-test bind-test
# mount -t tmpfs tmpfs bind-test/abc
#
** Description changed:
[Impact]
kubernetes loaded inactive dead transient mount points grows
https://github.com/kubernetes/kubernetes/issues/57345
[Test Case]
# cd /tmp
# mkdir -p bind-test/abc
# mount --bind bind-test bind-test
# mount -t tmpfs tmpfs bind-test/abc
#
** Description changed:
[Impact]
kubernetes loaded inactive dead transient mount points grows
https://github.com/kubernetes/kubernetes/issues/57345
[Test Case]
# cd /tmp
# mkdir -p bind-test/abc
# mount --bind bind-test bind-test
# mount -t tmpfs tmpfs bind-test/abc
#
Hello Joshua, or anyone else affected,
Accepted systemd into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21.11 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
[Impact]
kubernetes loaded inactive dead transient mount points grows
https://github.com/kubernetes/kubernetes/issues/57345
[Test Case]
- # cd /root
+ # cd /tmp
# mkdir -p bind-test/abc
# mount --bind bind-test bind-test
# mount -t tmpfs tmpfs
** Description changed:
+ [Impact]
+
+ kubernetes loaded inactive dead transient mount points grows
+ https://github.com/kubernetes/kubernetes/issues/57345
+
+ [Test Case]
+
+ # cd /tmp
+ # mkdir -p bind-test/abc
+ # mount --bind bind-test bind-test
+ # mount -t tmpfs tmpfs bind-test/abc
+
debdiff for xenial [systemd-lp1795764-xenial.debdiff]
** Patch added: "systemd-lp1795764-xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1795764/+attachment/5221471/+files/systemd-lp1795764-xenial.debdiff
--
You received this bug notification because you are a member
** Description changed:
From the PR:
Currently, if there are two /proc/self/mountinfo entries with the same
mount point path, the mount setup flags computed for the second of
these two entries will overwrite the mount setup flags computed for
the first of these two entries. This is the
I think the "|| true;" is a good test to validate but I might have to
find something more viable to SRU.
I'll see how upstream populate MOUNT(u)->just_mounted, and try to mimic
that as well instead of forcing "true" implicitly.
This is where I'm at the moment.
Stay tuned.
- Eric
--
You
We cannot cherrypick the fix as is. It has been introduced upstream[1]
inside a function and structure that not yet exist in 229[1].
Instead of backporting the whole thing (which seems unnecessary) we can
possibly mimic the upstream fix.
Basically, the upstream fix adds a "||
31 matches
Mail list logo
