Re: Bug#964541: flatpak: Wrong argument order for clone syscall seccomp filter on s390x
Control: tags -1 + upstream
Control: clone -1 -2 -3
Control: unblock 964150 by -2
Control: unblock 964150 by -3
Control: forwarded -1 https://github.com/flatpak/flatpak/pull/3777
Control: severity -2 normal
Control: reassign -2 src:webkit2gtk 2.28.4-1
Control: retitle -2 webkit2gtk: Wrong argument order for clone syscall seccomp filter on s390x
Control: severity -3 normal
Control: reassign -3 src:gnome-desktop3 3.36.4-1
Control: forwarded -3 https://gitlab.gnome.org/GNOME/gnome-desktop/-/merge_requests/82
Control: retitle -3 gnome-desktop3: Wrong argument order for clone syscall seccomp filter on s390x
On Thu, 06 Aug 2020 at 10:56:27 +0100, Simon McVittie wrote:
> I think for completeness we should also be testing __CRIS__
I've sent a patch upstream with that change and some extra comments.
If you have any suggested changes, please send them there.
> * gnome-desktop3_3.36.4-1/libgnome-desktop/gnome-desktop-thumbnail-script.c
Sent to https://gitlab.gnome.org/GNOME/gnome-desktop/-/merge_requests/82
> * systemd_246-2/src/shared/seccomp-util.c
On closer examination, this one is fine.
> * webkit2gtk_2.28.4-1/Source/WebKit/UIProcess/Launcher/glib/BubblewrapLauncher.cpp
I would appreciate it if a WebKit maintainer could look at this - the
code is not identical and I don't have the resources to compile WebKit.
Context for WebKit maintainers: see
I've also pinged Sandstorm as requested in the Flatpak source code.