This bug was fixed in the package systemd - 237-3ubuntu10.33
---
systemd (237-3ubuntu10.33) bionic; urgency=medium
*
d/p/lp1852754/0001-network-do-not-re-set-MTU-when-current-and-requested.patch,
d/p/lp1852754/0002-network-call-link_acquire_conf-and-link_enter_join_n.patch,
This bug was fixed in the package systemd - 240-6ubuntu5.8
---
systemd (240-6ubuntu5.8) disco; urgency=medium
[ Victor Tapia ]
* d/p/resolved_disable-connection-downgrade-when-DNSSEC-yes.patch
Fix regression introduced by
Just tested on bionic, looks good - thanks everyone!
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello Steve, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.32 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
OK, so my kernel didn't have seccomp support compiled in and systemd
just silently fails to set seccomp filters in that case.
Have now reproduced the bug on an armhf disco VM, and verified that the
package in proposed, 240-6ubuntu5.8 fixes it.
** Tags removed: verification-needed-disco
** Tags
OK, I've had a go, but oddly I can't reproduce this in a disco VM at the
moment, which makes testing the fix tricky..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840640
Title:
sync_file_range
@vorlon, will do my best to test the disco version, but I don't
currently have an ARM disco environment, and usual health battles mean
it'll probably be a struggle to set one up - I'll have a go though!
The bionic version I will of course be all over :)
--
You received this bug notification
Hello Steve, or anyone else affected,
Accepted systemd into disco-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/240-6ubuntu5.8
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
[impact]
calling the glibc function sync_file_range() on a armhf nspawn container
fails.
[test case]
see sample C program from original description below. compile and run
that inside a nspawn container on armhf and it will fail.
+
+ nspawn
The test case here should explain to the tester how to set up an nspawn
container to reproduce this.
** Changed in: systemd (Ubuntu Disco)
Status: In Progress => Incomplete
** Changed in: systemd (Ubuntu Bionic)
Status: In Progress => Incomplete
--
You received this bug
** Description changed:
- ARM has two sync_file_range syscalls, sync_file_range and
- sync_file_range2. The former is apparently not used, and glibc calls the
- latter whenever a userspace program calls sync_file_range. I'm guessing
- systemd-nspawn doesn't know this, because the follow code
> Is it possible arm64 abi is different from armhf (32bit?)
ah, that was it, thanks, I can reproduce it now :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840640
Title:
sync_file_range fails in
Can't check at the moment, but details should have been added by apport.
Is it possible arm64 abi is different from armhf (32bit?)
On Thu, 3 Oct 2019, 22:41 Dan Streetman,
wrote:
> I'm having trouble reproducing this on a Bionic nspawn container on
> arm64; what host release, and container
I'm having trouble reproducing this on a Bionic nspawn container on
arm64; what host release, and container release, are you using? Are you
using the latest glibc and systemd?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: systemd (Ubuntu Disco)
Assignee: (unassigned) => Dan Streetman (ddstreet)
** Changed in: systemd (Ubuntu Bionic)
Assignee: (unassigned) => Dan Streetman (ddstreet)
** Changed in: systemd (Ubuntu Disco)
Importance: Undecided => Medium
** Changed in: systemd (Ubuntu
** Tags removed: next-ddstreet
** Tags added: ddstreet disco
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840640
Title:
sync_file_range fails in nspawn containers on arm, ppc
To manage
** Also affects: systemd (Ubuntu Disco)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
** Tags added: next-ddstreet systemd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Test packages in case anyone wants them:
https://www.dropbox.com/sh/gxuy14k1t2chwbu/AABKX2idDrGu2R3Fwio0DAOTa?dl=0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840640
Title:
sync_file_range fails
this is cherrypickable, yes.
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840640
Title:
sync_file_range fails
https://github.com/systemd/systemd/pull/13352/commits/90ddac6087b5f8f3736364cfdf698e713f7e8869.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840640
Title:
sync_file_range fails in nspawn
20 matches
Mail list logo
