Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [PR PATCH] tor: update sandbox patch for ppc32
Date: Fri, 18 Oct 2019 19:49:01 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-15595@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 313 bytes --]

There is a new pull request by q66 against master on the void-packages repository

https://github.com/void-ppc/void-packages tor
https://github.com/void-linux/void-packages/pull/15595

tor: update sandbox patch for ppc32


A patch file from https://github.com/void-linux/void-packages/pull/15595.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-tor-15595.patch --]
[-- Type: text/x-diff, Size: 2207 bytes --]

From 06296580673d31a80d6d0ed78d76bfb897b73fc7 Mon Sep 17 00:00:00 2001
From: q66 <daniel@octaforge.org>
Date: Fri, 18 Oct 2019 19:30:36 +0200
Subject: [PATCH] tor: update sandbox patch for ppc32

[ci skip]
---
 srcpkgs/tor/patches/ppc.patch   | 35 +++++++++++++++++++++++++++++++++
 srcpkgs/tor/patches/ppc64.patch | 14 -------------
 2 files changed, 35 insertions(+), 14 deletions(-)
 create mode 100644 srcpkgs/tor/patches/ppc.patch
 delete mode 100644 srcpkgs/tor/patches/ppc64.patch

diff --git a/srcpkgs/tor/patches/ppc.patch b/srcpkgs/tor/patches/ppc.patch
new file mode 100644
index 00000000000..c72cdf6ad78
--- /dev/null
+++ b/srcpkgs/tor/patches/ppc.patch
@@ -0,0 +1,35 @@
+--- src/lib/sandbox/sandbox.c
++++ src/lib/sandbox/sandbox.c
+@@ -115,6 +115,16 @@
+ #define REG_SYSCALL 8
+ #define M_SYSCALL regs[REG_SYSCALL]
+ 
++#elif defined(__powerpc64__)
++
++#define REG_SYSCALL 0
++#define M_SYSCALL gp_regs[REG_SYSCALL]
++
++#elif defined(__powerpc__)
++
++#define REG_SYSCALL 0
++#define M_SYSCALL gregs[REG_SYSCALL]
++
+ #endif /* defined(__i386__) || ... */
+ 
+ /**Determines if at least one sandbox is active.*/
+@@ -1613,7 +1623,15 @@ sigsys_debugging(int nr, siginfo_t *info, void *void_context)
+   if (!ctx)
+     return;
+ 
++#if defined(__powerpc__) && !defined(__powerpc64__)
++#if defined(__GLIBC__)
++  syscall = (int) ctx->uc_mcontext.uc_regs->M_SYSCALL;
++#else
++  syscall = (int) ctx->uc_regs->M_SYSCALL;
++#endif
++#else
+   syscall = (int) ctx->uc_mcontext.M_SYSCALL;
++#endif
+ 
+ #ifdef USE_BACKTRACE
+   depth = backtrace(syscall_cb_buf, MAX_DEPTH);
diff --git a/srcpkgs/tor/patches/ppc64.patch b/srcpkgs/tor/patches/ppc64.patch
deleted file mode 100644
index aef2ba51f90..00000000000
--- a/srcpkgs/tor/patches/ppc64.patch
+++ /dev/null
@@ -1,14 +0,0 @@
---- src/lib/sandbox/sandbox.c	2018-12-20 17:33:15.815307612 +0100
-+++ src/lib/sandbox/sandbox.c	2018-12-20 17:36:59.795797024 +0100
-@@ -111,6 +111,11 @@
- #define REG_SYSCALL 8
- #define M_SYSCALL regs[REG_SYSCALL]
- 
-+#elif defined(__powerpc64__)
-+
-+#define REG_SYSCALL 0
-+#define M_SYSCALL gp_regs[REG_SYSCALL]
-+
- #endif /* defined(__i386__) || ... */
- 
- /**Determines if at least one sandbox is active.*/

             reply	other threads:[~2019-10-18 17:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-18 17:49 voidlinux-github [this message]
2019-10-18 18:32 ` [PR PATCH] [Merged]: " voidlinux-github

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-15595@inbox.vuxu.org \
    --to=voidlinux-github@inbox.vuxu.org \
    --cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).