From: Philipp Stephani <p.stephani2@gmail.com>
To: Glenn Morris <rgm@gnu.org>
Cc: Philipp Stephani <phst@google.com>, 47828@debbugs.gnu.org
Subject: bug#47828: seccomp test failures
Date: Mon, 19 Apr 2021 18:03:10 +0200 [thread overview]
Message-ID: <CAArVCkTAFbYzGgip1A8-EtWnDBdGHyRYi2CvdaZO6UwmYJcO_w@mail.gmail.com> (raw)
In-Reply-To: <CAArVCkQg9NCK-wv4s7TKwrt-ShHazzJD214V1bqsJ1JBcZ=RQw@mail.gmail.com>
Am Mo., 19. Apr. 2021 um 18:00 Uhr schrieb Philipp Stephani
<p.stephani2@gmail.com>:
>
> Am Mo., 19. Apr. 2021 um 17:49 Uhr schrieb Glenn Morris <rgm@gnu.org>:
> >
> > Philipp Stephani wrote:
> >
> > >> IIUC, it's arch_prctl.
> > >
> > > What's the subfunction (first argument)? From looking at the glibc
> > > sources it could be ARCH_CET_STATUS (0x3001).
> >
> > How do I find that out?
>
> I've often had success with installing the debug symbols for the
> libraries in question (often they are in a separate package) and then
> using coredumpctl debug to drop into GDB.
Or alternatively, add a rule like
RULE (SCMP_ACT_ALLOW, SCMP_SYS (arch_prctl),
SCMP_A0_32 (SCMP_CMP_EQ, 0x3001));
to line 350 of lib-src/seccomp-filter.c and check whether it fixes the problem.
next prev parent reply other threads:[~2021-04-19 16:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-16 16:53 bug#47828: seccomp test failures Glenn Morris
2021-04-17 18:21 ` Philipp Stephani
2021-04-17 19:54 ` Philipp Stephani
2021-04-18 0:01 ` Glenn Morris
2021-04-18 8:32 ` Philipp Stephani
2021-04-18 8:36 ` Philipp Stephani
2021-04-18 16:19 ` Glenn Morris
2021-04-18 17:16 ` Philipp Stephani
2021-04-18 21:58 ` Glenn Morris
2021-04-19 8:36 ` Philipp Stephani
2021-04-19 15:49 ` Glenn Morris
2021-04-19 16:00 ` Philipp Stephani
2021-04-19 16:03 ` Philipp Stephani [this message]
2021-04-19 16:39 ` Glenn Morris
2021-04-19 19:31 ` Philipp Stephani
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=CAArVCkTAFbYzGgip1A8-EtWnDBdGHyRYi2CvdaZO6UwmYJcO_w@mail.gmail.com \
--to=p.stephani2@gmail.com \
--cc=47828@debbugs.gnu.org \
--cc=phst@google.com \
--cc=rgm@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.