[Touch-packages] [Bug 1944436] Re: Please backport support for "close_range" syscall

2022-01-12 Thread Dan Nicholson
This causes an issue when using glib's gspawn APIs under libseccomp on
impish. It uses close_range to set CLOEXEC on some open file descriptors
and rightfully checks for ENOSYS. However, since seccomp doesn't know
about the syscall that becomes EPERM and it skips setting CLOEXEC
assuming there was a legit error in close_range. Eventually this means
that the process run by gspawn hangs because nothing is closing the file
descriptor as expected.

Debian has been shipping this backported to bullseye for a while -
https://salsa.debian.org/debian/libseccomp/-/blob/debian/bullseye/debian/patches/syscalls_add_close_range_syscall.patch.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/1944436

Title:
  Please backport support for "close_range" syscall

Status in libseccomp package in Ubuntu:
  New

Bug description:
  Please backport support for the "close_range" syscall .. may be as
  simple as cherrypicking

  
https://github.com/seccomp/libseccomp/commit/01e5750e7c84bb14e5a5410c924bed519209db06

  from upstream. I've hit problems running buildah in a systemd-nspawn
  container, but this will probably affect people trying to run modern
  code in other container systems as well, e.g. docker.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libseccomp2 2.5.1-1ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-84.94-generic 5.4.133
  Uname: Linux 5.4.0-84-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Xpra
  Date: Tue Sep 21 15:10:54 2021
  InstallationDate: Installed on 2017-01-08 (1717 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: libseccomp
  UpgradeStatus: Upgraded to focal on 2021-09-02 (19 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1944436/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1956059] [NEW] Backport gspawn fixes to impish

2021-12-30 Thread Dan Nicholson
Public bug reported:

A few changes for gspawn landed in the 2.67 series that had some bugs
which were later fixed and backported to 2.70 as seen in
https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2394. These bugs
are present in 2.68 as on impish, but that series won't see any more
updates upstream.

Currently this is causing a bug in the OSTree test suite as seen in
https://github.com/ostreedev/ostree/issues/2495 with
https://github.com/ostreedev/ostree/issues/2495#issuecomment-1000247260
confirming from glib's maintainer that these bugs are likely the issue.

Attached is a debdiff with the 3 patches that were backported to 2.70.

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "Debdiff for 3 gspawn backport patches"
   
https://bugs.launchpad.net/bugs/1956059/+attachment/5550436/+files/glib2.0_2.68.4-1ubuntu2.diff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1956059

Title:
  Backport gspawn fixes to impish

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  A few changes for gspawn landed in the 2.67 series that had some bugs
  which were later fixed and backported to 2.70 as seen in
  https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2394. These bugs
  are present in 2.68 as on impish, but that series won't see any more
  updates upstream.

  Currently this is causing a bug in the OSTree test suite as seen in
  https://github.com/ostreedev/ostree/issues/2495 with
  https://github.com/ostreedev/ostree/issues/2495#issuecomment-1000247260
  confirming from glib's maintainer that these bugs are likely the
  issue.

  Attached is a debdiff with the 3 patches that were backported to 2.70.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1956059/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp