since the patch to fix this relies on conservative_rename(), which isn't
present in bionic, as well as this bug being mostly an annoyance that
can be ignored, i'm marking as wont-fix for bionic
** Changed in: systemd (Ubuntu Bionic)
Status: Confirmed => Won't Fix
--
You received this bug
This bug was fixed in the package systemd - 247.3-3ubuntu3.4
---
systemd (247.3-3ubuntu3.4) hirsute-security; urgency=medium
* SECURITY UPDATE: DoS via DHCP FORCERENEW
- debian/patches/CVE-2020-13529.patch: tentatively ignore FORCERENEW
command in
This bug was fixed in the package systemd - 245.4-4ubuntu3.10
---
systemd (245.4-4ubuntu3.10) focal-security; urgency=medium
* SECURITY UPDATE: DoS via DHCP FORCERENEW
- debian/patches/CVE-2020-13529.patch: tentatively ignore FORCERENEW
command in
This bug was fixed in the package systemd - 246.6-1ubuntu1.5
---
systemd (246.6-1ubuntu1.5) groovy; urgency=medium
[ Kai-Heng Feng ]
* d/p/lp1930910-hwdb-Add-ProBook-to-use-micmute-hotkey.patch:
- Add ProBook to use micmute hotkey (LP: #1930910)
Confirmed fixed on lxd02 and client site, running Focal. No reboot was
done.
Thank you.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1891215
Title:
systemd-resolved
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
> that was the atime
yep, really no way around updating the atime, as systemd of course needs
to access the file to check if the content is the same or not
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Verification for Groovy (246.6-1ubuntu1.5)
# Initial repro on groovy:
root@groovy:~# md5sum /etc/resolv.conf; stat -t -L /etc/resolv.conf
6b21d96b644bdafc7a3094fe04ab4e88 /etc/resolv.conf
/etc/resolv.conf 729 8 81a4 102 104 8f 111 1 0 0 1625844827 1625844823
1625844823 0 4096
root@groovy:~#
Verification for Focal (245.4-4ubuntu3.8)
# Initial repro on focal:
root@focal:~# md5sum /etc/resolv.conf; stat -t -L /etc/resolv.conf
fbfde622ae28a4dcfbf73a397a10c6ae /etc/resolv.conf
/etc/resolv.conf 717 8 81a4 101 103 76 123 1 0 0 1625844292 1625844273
1625844273 0 4096
root@focal:~# ip
Sorry about the noise, I had a problem in my reproducing steps, the
previous comment should be ignored. I got confused by stat's output
changing but that was the atime, not the mtime that was changing.
** Tags removed: verification-failed-focal
** Tags added: verification-needed-focal
--
You
@ddstreet, unfortunately, even with 245.4-4ubuntu3.8 on Focal, the mtime
keeps changing as RAs are received :/
** Tags removed: verification-needed-focal
** Tags added: verification-failed-focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Hello Simon, or anyone else affected,
Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.8 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Simon, or anyone else affected,
Accepted systemd into groovy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/246.6-1ubuntu1.5 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Simon, or anyone else affected,
Accepted systemd into hirsute-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/systemd/247.3-3ubuntu3.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
[impact]
networking changes, like RA events, can cause systemd-resolved to re-
write the resolv.conf file, even if the contents didn't change,
resulting in unnecessary increased amount of inotify events
[test case]
see original description for
> whereas in truth the combination of
https://github.com/systemd/systemd/pull/17535 and its networkd
counterpart did not resolve it.
This statement is most probably not correct: what I meant is that the
changes made upstream did not resolve our issue.
Because the issue was fixed upstream a few
** Description changed:
[impact]
networking changes, like RA events, can cause systemd-resolved to re-
write the resolv.conf file, even if the contents didn't change,
resulting in unnecessary increased amount of inotify events
[test case]
- see original description
+ see
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Bionic)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
** Also affects: systemd via
https://github.com/systemd/systemd/issues/17577
Importance: Unknown
Status: Unknown
** Description changed:
+ [impact]
+
+ networking changes, like RA events, can cause systemd-resolved to re-
+ write the resolv.conf file, even if the contents didn't
Hello,
Some days ago, I installed systemd-dbgsym_245.4-4ubuntu3.6_amd64.ddeb
and set a breakpoint on function
'conservative_renameat':https://github.com/systemd/systemd/blob/main/src/basic
/fs-util.c#L1504 (because of my understanding of function
> Problem is still occuring.
thanks, but my question was if you'd opened an upstream bug, since this
needs to be fixed upstream first.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
On the same machine as sdeziel found the problem:
root@lxd02:~# lsb_release -rd
Description:Ubuntu 20.04.2 LTS
Release:20.04
root@lxd02:~# apt-cache policy systemd
systemd:
Installed: 245.4-4ubuntu3.7
Candidate: 245.4-4ubuntu3.7
Version table:
*** 245.4-4ubuntu3.7 500
I no longer have access to the affected machine(s) so I'll mark it as
incomplete waiting for an ex-colleague to check if the problem still
occurs.
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch
this needs to be fixed upstream first, have you opened an upstream bug?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1891215
Title:
systemd-resolved re-creates
** Changed in: systemd (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1891215
Title:
systemd-resolved re-creates
strace'ing systemd-resolved showed that files under
/run/systemd/netif/links/ are re-created as well when a RA comes in but
their content never changes yet the stub-resolv.conf is created over and
over:
root@lxd02:~# cat /run/systemd/netif/links/*
/run/systemd/resolve/stub-resolv.conf | md5sum;
26 matches
Mail list logo
