| 2016-06-05 17:58:43 |
Tamas Papp |
bug |
|
|
added bug |
| 2016-06-13 13:58:11 |
Launchpad Janitor |
util-linux (Ubuntu): status |
New |
Confirmed |
|
| 2016-06-13 13:58:15 |
Michael Stucki |
bug |
|
|
added subscriber Michael Stucki |
| 2016-06-25 16:07:39 |
Alberto Salvia Novella |
util-linux (Ubuntu): importance |
Undecided |
Medium |
|
| 2016-07-31 18:39:54 |
Anders Sandblad |
bug |
|
|
added subscriber Anders Sandblad |
| 2016-09-05 05:15:56 |
Johan Ehnberg |
description |
fstrun daily cronjob output in an unprivileged LXD container:
/etc/cron.weekly/fstrim:
fstrim: cannot open /dev/.lxd-mounts: Permission denied
fstrim: /dev/fuse: not a directory
fstrim: /dev/lxd: FITRIM ioctl failed: Operation not permitted
There is a github issue:
https://github.com/lxc/lxd/issues/2030
The outcome is that it's purely an fstrim misbehaviour, it could be smarter.
Stephane Graber comment:
As all of this is handled by the kernel, there isn't anything we can do about it in LXD.
I think fstrim should be made slightly more clever:
* Don't run on bind-mounts (you can detect bind-mounts by parsing /proc/self/mountinfo instead of /proc/mounts)
* Maybe not be as noisy on expected errors like EACCES, EPERM and ENOENT, only log actual failures which would likely be EINVAL or memory related errors.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: util-linux 2.27.1-6ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Sun Jun 5 19:49:04 2016
ProcEnviron:
LANGUAGE=en_US:en
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: util-linux
UpgradeStatus: No upgrade log present (probably fresh install) |
fstrun weekly cronjob output in an unprivileged LXD container:
/etc/cron.weekly/fstrim:
fstrim: cannot open /dev/.lxd-mounts: Permission denied
fstrim: /dev/fuse: not a directory
fstrim: /dev/lxd: FITRIM ioctl failed: Operation not permitted
There is a github issue:
https://github.com/lxc/lxd/issues/2030
The outcome is that it's purely an fstrim misbehaviour, it could be smarter.
Stephane Graber comment:
As all of this is handled by the kernel, there isn't anything we can do about it in LXD.
I think fstrim should be made slightly more clever:
* Don't run on bind-mounts (you can detect bind-mounts by parsing /proc/self/mountinfo instead of /proc/mounts)
* Maybe not be as noisy on expected errors like EACCES, EPERM and ENOENT, only log actual failures which would likely be EINVAL or memory related errors.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: util-linux 2.27.1-6ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Sun Jun 5 19:49:04 2016
ProcEnviron:
LANGUAGE=en_US:en
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: util-linux
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2016-12-05 09:58:43 |
Will Bryant |
bug |
|
|
added subscriber Will Bryant |
| 2017-01-15 13:23:57 |
Luis Felipe Marzagao |
bug |
|
|
added subscriber Luis Felipe Marzagao |
| 2017-01-29 17:33:26 |
Simon Déziel |
bug |
|
|
added subscriber Simon Déziel |
| 2017-01-29 17:33:52 |
Simon Déziel |
description |
fstrun weekly cronjob output in an unprivileged LXD container:
/etc/cron.weekly/fstrim:
fstrim: cannot open /dev/.lxd-mounts: Permission denied
fstrim: /dev/fuse: not a directory
fstrim: /dev/lxd: FITRIM ioctl failed: Operation not permitted
There is a github issue:
https://github.com/lxc/lxd/issues/2030
The outcome is that it's purely an fstrim misbehaviour, it could be smarter.
Stephane Graber comment:
As all of this is handled by the kernel, there isn't anything we can do about it in LXD.
I think fstrim should be made slightly more clever:
* Don't run on bind-mounts (you can detect bind-mounts by parsing /proc/self/mountinfo instead of /proc/mounts)
* Maybe not be as noisy on expected errors like EACCES, EPERM and ENOENT, only log actual failures which would likely be EINVAL or memory related errors.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: util-linux 2.27.1-6ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Sun Jun 5 19:49:04 2016
ProcEnviron:
LANGUAGE=en_US:en
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: util-linux
UpgradeStatus: No upgrade log present (probably fresh install) |
fstrim weekly cronjob output in an unprivileged LXD container:
/etc/cron.weekly/fstrim:
fstrim: cannot open /dev/.lxd-mounts: Permission denied
fstrim: /dev/fuse: not a directory
fstrim: /dev/lxd: FITRIM ioctl failed: Operation not permitted
There is a github issue:
https://github.com/lxc/lxd/issues/2030
The outcome is that it's purely an fstrim misbehaviour, it could be smarter.
Stephane Graber comment:
As all of this is handled by the kernel, there isn't anything we can do about it in LXD.
I think fstrim should be made slightly more clever:
* Don't run on bind-mounts (you can detect bind-mounts by parsing /proc/self/mountinfo instead of /proc/mounts)
* Maybe not be as noisy on expected errors like EACCES, EPERM and ENOENT, only log actual failures which would likely be EINVAL or memory related errors.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: util-linux 2.27.1-6ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Sun Jun 5 19:49:04 2016
ProcEnviron:
LANGUAGE=en_US:en
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: util-linux
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2017-02-22 09:16:48 |
Alex Bachmeier |
bug |
|
|
added subscriber Alex Bachmeier |
| 2017-04-03 07:26:05 |
Rune Juhl Jacobsen |
bug |
|
|
added subscriber Rune Juhl Jacobsen |
| 2017-06-06 07:09:01 |
André Bauer |
bug |
|
|
added subscriber André Bauer |
| 2017-06-06 13:26:06 |
Hans Deragon |
bug |
|
|
added subscriber Hans Deragon |
| 2017-09-03 20:14:16 |
Ivan Kurnosov |
bug |
|
|
added subscriber Ivan Kurnosov |
| 2018-04-10 20:32:49 |
Jose Manuel Santamaria Lema |
bug |
|
|
added subscriber Jose Manuel Santamaria Lema |
| 2019-08-14 17:07:19 |
Eric Desrochers |
bug watch added |
|
https://github.com/karelzak/util-linux/issues/840 |
|
| 2019-08-14 19:50:03 |
Tianon Gravi |
bug |
|
|
added subscriber Tianon Gravi |
| 2019-08-15 15:23:45 |
Eric Desrochers |
util-linux (Ubuntu): status |
Confirmed |
In Progress |
|
| 2019-08-15 15:23:48 |
Eric Desrochers |
util-linux (Ubuntu): assignee |
|
Eric Desrochers (slashd) |
|
| 2019-08-20 14:07:31 |
Eric Desrochers |
nominated for series |
|
Ubuntu Bionic |
|
| 2019-08-20 14:07:31 |
Eric Desrochers |
bug task added |
|
util-linux (Ubuntu Bionic) |
|
| 2019-08-20 14:07:31 |
Eric Desrochers |
nominated for series |
|
Ubuntu Disco |
|
| 2019-08-20 14:07:31 |
Eric Desrochers |
bug task added |
|
util-linux (Ubuntu Disco) |
|
| 2019-08-20 14:07:31 |
Eric Desrochers |
nominated for series |
|
Ubuntu Xenial |
|
| 2019-08-20 14:07:31 |
Eric Desrochers |
bug task added |
|
util-linux (Ubuntu Xenial) |
|
| 2019-08-20 14:07:48 |
Eric Desrochers |
util-linux (Ubuntu Xenial): assignee |
|
Eric Desrochers (slashd) |
|
| 2019-08-20 14:07:51 |
Eric Desrochers |
util-linux (Ubuntu Xenial): status |
New |
In Progress |
|
| 2019-08-20 14:07:56 |
Eric Desrochers |
util-linux (Ubuntu Bionic): assignee |
|
Eric Desrochers (slashd) |
|
| 2019-08-20 14:07:58 |
Eric Desrochers |
util-linux (Ubuntu Disco): assignee |
|
Eric Desrochers (slashd) |
|
| 2019-08-20 14:08:01 |
Eric Desrochers |
util-linux (Ubuntu Xenial): importance |
Undecided |
Medium |
|
| 2019-08-20 14:08:03 |
Eric Desrochers |
util-linux (Ubuntu Bionic): importance |
Undecided |
Medium |
|
| 2019-08-20 14:08:05 |
Eric Desrochers |
util-linux (Ubuntu Disco): importance |
Undecided |
Medium |
|
| 2019-08-20 14:14:17 |
Eric Desrochers |
description |
fstrim weekly cronjob output in an unprivileged LXD container:
/etc/cron.weekly/fstrim:
fstrim: cannot open /dev/.lxd-mounts: Permission denied
fstrim: /dev/fuse: not a directory
fstrim: /dev/lxd: FITRIM ioctl failed: Operation not permitted
There is a github issue:
https://github.com/lxc/lxd/issues/2030
The outcome is that it's purely an fstrim misbehaviour, it could be smarter.
Stephane Graber comment:
As all of this is handled by the kernel, there isn't anything we can do about it in LXD.
I think fstrim should be made slightly more clever:
* Don't run on bind-mounts (you can detect bind-mounts by parsing /proc/self/mountinfo instead of /proc/mounts)
* Maybe not be as noisy on expected errors like EACCES, EPERM and ENOENT, only log actual failures which would likely be EINVAL or memory related errors.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: util-linux 2.27.1-6ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Sun Jun 5 19:49:04 2016
ProcEnviron:
LANGUAGE=en_US:en
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: util-linux
UpgradeStatus: No upgrade log present (probably fresh install) |
[Impact]
fstrim weekly cronjob output in an unprivileged LXD container:
/etc/cron.weekly/fstrim:
fstrim: cannot open /dev/.lxd-mounts: Permission denied
fstrim: /dev/fuse: not a directory
fstrim: /dev/lxd: FITRIM ioctl failed: Operation not permitted
There is a github issue:
https://github.com/lxc/lxd/issues/2030
The outcome is that it's purely an fstrim misbehaviour, it could be smarter.
Stephane Graber comment:
As all of this is handled by the kernel, there isn't anything we can do about it in LXD.
I think fstrim should be made slightly more clever:
* Don't run on bind-mounts (you can detect bind-mounts by parsing /proc/self/mountinfo instead of /proc/mounts)
* Maybe not be as noisy on expected errors like EACCES, EPERM and ENOENT, only log actual failures which would likely be EINVAL or memory related errors.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: util-linux 2.27.1-6ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Sun Jun 5 19:49:04 2016
ProcEnviron:
LANGUAGE=en_US:en
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: util-linux
UpgradeStatus: No upgrade log present (probably fresh install)
[Test Case]
* Ubuntu lxd container
* Wait for the scheduled fstrim run (X: cronjob, B and late: systemd timer)
* fstrim will run and report errors "Operation not permitted" "Permission denied", ...
Container shouldn't run fstrim, it should only be run at host level.
[Potential Regression]
None, the change will only block fstrim to be automatically run at scheduled time.
Xenial uses the cronjob approach /etc/cron.weekly/fstrim
Bionic and late switched to a systemd timer.
2 differents fixes (one for X, and one for B and late) will be needed, but they'll do same thing, which prevent fstrim to automatically run if inside a container both fixes using systemd-virt-detect.
[Other Informations]
* The systemd timer change upstream PR:
https://github.com/karelzak/util-linux/pull/841 |
|
| 2019-08-20 14:14:26 |
Eric Desrochers |
tags |
amd64 apport-bug xenial |
amd64 apport-bug sts xenial |
|
| 2019-08-20 14:21:00 |
Launchpad Janitor |
util-linux (Ubuntu Bionic): status |
New |
Confirmed |
|
| 2019-08-20 14:21:00 |
Launchpad Janitor |
util-linux (Ubuntu Disco): status |
New |
Confirmed |
|
| 2019-08-20 14:24:12 |
Eric Desrochers |
util-linux (Ubuntu Bionic): status |
Confirmed |
In Progress |
|
| 2019-08-20 14:24:14 |
Eric Desrochers |
util-linux (Ubuntu Disco): status |
Confirmed |
In Progress |
|
| 2019-08-20 14:25:44 |
Eric Desrochers |
description |
[Impact]
fstrim weekly cronjob output in an unprivileged LXD container:
/etc/cron.weekly/fstrim:
fstrim: cannot open /dev/.lxd-mounts: Permission denied
fstrim: /dev/fuse: not a directory
fstrim: /dev/lxd: FITRIM ioctl failed: Operation not permitted
There is a github issue:
https://github.com/lxc/lxd/issues/2030
The outcome is that it's purely an fstrim misbehaviour, it could be smarter.
Stephane Graber comment:
As all of this is handled by the kernel, there isn't anything we can do about it in LXD.
I think fstrim should be made slightly more clever:
* Don't run on bind-mounts (you can detect bind-mounts by parsing /proc/self/mountinfo instead of /proc/mounts)
* Maybe not be as noisy on expected errors like EACCES, EPERM and ENOENT, only log actual failures which would likely be EINVAL or memory related errors.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: util-linux 2.27.1-6ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Sun Jun 5 19:49:04 2016
ProcEnviron:
LANGUAGE=en_US:en
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: util-linux
UpgradeStatus: No upgrade log present (probably fresh install)
[Test Case]
* Ubuntu lxd container
* Wait for the scheduled fstrim run (X: cronjob, B and late: systemd timer)
* fstrim will run and report errors "Operation not permitted" "Permission denied", ...
Container shouldn't run fstrim, it should only be run at host level.
[Potential Regression]
None, the change will only block fstrim to be automatically run at scheduled time.
Xenial uses the cronjob approach /etc/cron.weekly/fstrim
Bionic and late switched to a systemd timer.
2 differents fixes (one for X, and one for B and late) will be needed, but they'll do same thing, which prevent fstrim to automatically run if inside a container both fixes using systemd-virt-detect.
[Other Informations]
* The systemd timer change upstream PR:
https://github.com/karelzak/util-linux/pull/841 |
[Impact]
fstrim weekly cronjob output in an unprivileged LXD container:
/etc/cron.weekly/fstrim:
fstrim: cannot open /dev/.lxd-mounts: Permission denied
fstrim: /dev/fuse: not a directory
fstrim: /dev/lxd: FITRIM ioctl failed: Operation not permitted
There is a github issue:
https://github.com/lxc/lxd/issues/2030
The outcome is that it's purely an fstrim misbehaviour, it could be smarter.
Stephane Graber comment:
As all of this is handled by the kernel, there isn't anything we can do about it in LXD.
I think fstrim should be made slightly more clever:
* Don't run on bind-mounts (you can detect bind-mounts by parsing /proc/self/mountinfo instead of /proc/mounts)
* Maybe not be as noisy on expected errors like EACCES, EPERM and ENOENT, only log actual failures which would likely be EINVAL or memory related errors.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: util-linux 2.27.1-6ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Sun Jun 5 19:49:04 2016
ProcEnviron:
LANGUAGE=en_US:en
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: util-linux
UpgradeStatus: No upgrade log present (probably fresh install)
[Test Case]
* Ubuntu lxd container
* Wait for the scheduled fstrim run (X: cronjob, B and late: systemd timer)
* fstrim will run and report errors "Operation not permitted" "Permission denied", ...
Container shouldn't run fstrim, it should only be run at host level.
[Potential Regression]
None, the change will only block fstrim to be automatically run at scheduled time. One can still run fstrim on a container manually, even if there is no purpose of doing that.
Xenial uses the cronjob approach /etc/cron.weekly/fstrim
Bionic and late switched to a systemd timer.
2 differents fixes (one for X, and one for B and late) will be needed, but they'll do same thing, which prevent fstrim to automatically run if inside a container both fixes using systemd-virt-detect.
[Other Informations]
* The systemd timer change upstream PR:
https://github.com/karelzak/util-linux/pull/841 |
|
| 2019-08-20 18:57:47 |
Mitar |
bug |
|
|
added subscriber Mitar |
| 2019-08-21 16:31:32 |
Eric Desrochers |
bug watch added |
|
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935326 |
|
| 2019-08-21 16:31:32 |
Eric Desrochers |
bug task added |
|
util-linux (Debian) |
|
| 2019-08-22 23:40:03 |
Launchpad Janitor |
util-linux (Ubuntu): status |
In Progress |
Fix Released |
|
| 2019-08-23 11:20:07 |
Timo Aaltonen |
util-linux (Ubuntu Disco): status |
In Progress |
Fix Committed |
|
| 2019-08-23 11:20:10 |
Timo Aaltonen |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2019-08-23 11:20:12 |
Timo Aaltonen |
bug |
|
|
added subscriber SRU Verification |
| 2019-08-23 11:21:24 |
Timo Aaltonen |
util-linux (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
| 2019-08-23 11:24:50 |
Timo Aaltonen |
util-linux (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2019-08-27 14:07:44 |
Eric Desrochers |
tags |
amd64 apport-bug sts xenial |
amd64 apport-bug sts verification-done-bionic verification-needed-disco verification-needed-xenial xenial |
|
| 2019-08-27 14:20:51 |
Eric Desrochers |
tags |
amd64 apport-bug sts verification-done-bionic verification-needed-disco verification-needed-xenial xenial |
amd64 apport-bug sts verification-done-bionic verification-done-disco verification-done-xenial xenial |
|
| 2019-08-27 14:24:41 |
Eric Desrochers |
description |
[Impact]
fstrim weekly cronjob output in an unprivileged LXD container:
/etc/cron.weekly/fstrim:
fstrim: cannot open /dev/.lxd-mounts: Permission denied
fstrim: /dev/fuse: not a directory
fstrim: /dev/lxd: FITRIM ioctl failed: Operation not permitted
There is a github issue:
https://github.com/lxc/lxd/issues/2030
The outcome is that it's purely an fstrim misbehaviour, it could be smarter.
Stephane Graber comment:
As all of this is handled by the kernel, there isn't anything we can do about it in LXD.
I think fstrim should be made slightly more clever:
* Don't run on bind-mounts (you can detect bind-mounts by parsing /proc/self/mountinfo instead of /proc/mounts)
* Maybe not be as noisy on expected errors like EACCES, EPERM and ENOENT, only log actual failures which would likely be EINVAL or memory related errors.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: util-linux 2.27.1-6ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Sun Jun 5 19:49:04 2016
ProcEnviron:
LANGUAGE=en_US:en
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: util-linux
UpgradeStatus: No upgrade log present (probably fresh install)
[Test Case]
* Ubuntu lxd container
* Wait for the scheduled fstrim run (X: cronjob, B and late: systemd timer)
* fstrim will run and report errors "Operation not permitted" "Permission denied", ...
Container shouldn't run fstrim, it should only be run at host level.
[Potential Regression]
None, the change will only block fstrim to be automatically run at scheduled time. One can still run fstrim on a container manually, even if there is no purpose of doing that.
Xenial uses the cronjob approach /etc/cron.weekly/fstrim
Bionic and late switched to a systemd timer.
2 differents fixes (one for X, and one for B and late) will be needed, but they'll do same thing, which prevent fstrim to automatically run if inside a container both fixes using systemd-virt-detect.
[Other Informations]
* The systemd timer change upstream PR:
https://github.com/karelzak/util-linux/pull/841 |
[Impact]
fstrim weekly cronjob output in an unprivileged LXD container:
/etc/cron.weekly/fstrim:
fstrim: cannot open /dev/.lxd-mounts: Permission denied
fstrim: /dev/fuse: not a directory
fstrim: /dev/lxd: FITRIM ioctl failed: Operation not permitted
There is a github issue:
https://github.com/lxc/lxd/issues/2030
The outcome is that it's purely an fstrim misbehaviour, it could be smarter.
Stephane Graber comment:
As all of this is handled by the kernel, there isn't anything we can do about it in LXD.
I think fstrim should be made slightly more clever:
* Don't run on bind-mounts (you can detect bind-mounts by parsing /proc/self/mountinfo instead of /proc/mounts)
* Maybe not be as noisy on expected errors like EACCES, EPERM and ENOENT, only log actual failures which would likely be EINVAL or memory related errors.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: util-linux 2.27.1-6ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Sun Jun 5 19:49:04 2016
ProcEnviron:
LANGUAGE=en_US:en
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: util-linux
UpgradeStatus: No upgrade log present (probably fresh install)
[Test Case]
* Ubuntu lxd container
* Wait for the scheduled fstrim run (X: cronjob, B and late: systemd timer)
* fstrim will run and report errors "Operation not permitted" "Permission denied", ...
Container shouldn't run fstrim, it should only be run at host level.
[Potential Regression]
None, the change will only block fstrim to be automatically run at scheduled time. One can still run fstrim on a container manually, even if there is no purpose of doing that.
Xenial uses the cronjob approach /etc/cron.weekly/fstrim
Bionic and late switched to a systemd timer.
2 differents fixes (one for X, and one for B and late) will be needed, but they'll do same thing, which prevent fstrim to automatically run if inside a container both fixes using systemd-virt-detect.
[Other Informations]
* The systemd timer change upstream PR:
https://github.com/karelzak/util-linux/pull/841
https://github.com/karelzak/util-linux/commit/0280d31a2bd6292acd9a4b86d0f6b5feb275a618 |
|
| 2019-08-27 19:26:11 |
Eric Desrochers |
cve linked |
|
2019-5867 |
|
| 2019-08-27 19:26:11 |
Eric Desrochers |
cve linked |
|
2019-5868 |
|
| 2019-09-02 08:53:05 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2019-09-02 09:03:09 |
Launchpad Janitor |
util-linux (Ubuntu Disco): status |
Fix Committed |
Fix Released |
|
| 2019-09-02 09:12:23 |
Launchpad Janitor |
util-linux (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2019-09-03 04:49:03 |
Bug Watch Updater |
util-linux (Debian): status |
Unknown |
New |
|
| 2019-09-04 14:56:02 |
Launchpad Janitor |
util-linux (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2019-09-05 05:31:04 |
Bug Watch Updater |
util-linux (Debian): status |
New |
Confirmed |
|
| 2020-05-04 14:21:17 |
Bug Watch Updater |
util-linux (Debian): status |
Confirmed |
Fix Released |
|
