From: "Peter Müller" <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 4b8ae872584947c0527eb5f76f06444f7b060cb4
Date: Sat, 09 Apr 2022 08:27:56 +0000 [thread overview]
Message-ID: <4Kb7Xs12Mdz2xjF@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2281 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, next has been updated
via 4b8ae872584947c0527eb5f76f06444f7b060cb4 (commit)
from 83c8662be8de15771ae6c7a5c287dc915a151b50 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 4b8ae872584947c0527eb5f76f06444f7b060cb4
Author: Peter Müller <peter.mueller(a)ipfire.org>
Date: Sat Apr 9 08:27:03 2022 +0000
Tor: glibc needs rseq syscall as well
Fixes: #12807 (finally)
Tested-by: Peter Müller <peter.mueller(a)ipfire.org>
Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
src/patches/Tor-Sandbox-permit-the-clone3-system-call.patch | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
Difference in files:
diff --git a/src/patches/Tor-Sandbox-permit-the-clone3-system-call.patch b/src/patches/Tor-Sandbox-permit-the-clone3-system-call.patch
index e8c6957f2..7e819ce73 100644
--- a/src/patches/Tor-Sandbox-permit-the-clone3-system-call.patch
+++ b/src/patches/Tor-Sandbox-permit-the-clone3-system-call.patch
@@ -1,13 +1,14 @@
diff -Naur tor-0.4.6.10.orig/src/lib/sandbox/sandbox.c tor-0.4.6.10/src/lib/sandbox/sandbox.c
---- tor-0.4.6.10.orig/src/lib/sandbox/sandbox.c 2022-03-31 07:17:55.966217291 +0000
-+++ tor-0.4.6.10/src/lib/sandbox/sandbox.c 2022-03-31 07:19:23.730134367 +0000
-@@ -151,6 +151,9 @@
+--- tor-0.4.6.10.orig/src/lib/sandbox/sandbox.c 2022-04-09 07:58:00.281189564 +0000
++++ tor-0.4.6.10/src/lib/sandbox/sandbox.c 2022-04-09 08:00:55.861698856 +0000
+@@ -151,6 +151,10 @@
SCMP_SYS(clock_gettime),
SCMP_SYS(close),
SCMP_SYS(clone),
+#ifdef __NR_clone3
+ SCMP_SYS(clone3),
+#endif
++ SCMP_SYS(rseq),
SCMP_SYS(dup),
SCMP_SYS(epoll_create),
SCMP_SYS(epoll_wait),
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2022-04-09 8:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4Kb7Xs12Mdz2xjF@people01.haj.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox