mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Clemens Gruber <clemens.gruber@pqgruber.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] systemd: seccomp
Date: Sun, 20 Dec 2015 16:30:03 +0100	[thread overview]
Message-ID: <20151220153003.GC25555@archie.tuxnet.lan> (raw)
In-Reply-To: <20151129154713.GC10431@pengutronix.de>

Hi,

On Sun, Nov 29, 2015 at 04:47:13PM +0100, Uwe Kleine-König wrote:
> Hello,
> 
> On Sun, Nov 29, 2015 at 04:21:32PM +0100, Clemens Gruber wrote:
> > I noticed that the systemd rule in ptxdist explicitly disables seccomp
> > support. Would be great to have support for SystemCallFilter in service
> > files.
> > 
> > I therefore added libseccomp and modified the systemd rule to enable
> > seccomp (optionally via a menu entry).
> > I use the current git master Linux kernel with CONFIG_SECCOMP enabled.
> > 
> > Even though systemctl --version shows +SECCOMP, the SystemCallFilter
> > statement does not have any effect.
> > For testing, I only allowed one syscall for a program which needs much
> > more, but it did still run normally as if no SystemCallFilter had been
> > set at all.
> > 
> > Platform used:
> > - ARM (i.MX6Q) with ptxdist: SystemCallFilter had no effect
> > - x86_64 (Intel i7 6700K) with ArchLinux: Working perfectly
> the obvious cross test is to test arch on your i.MX6 and a ptxdist
> generated os on your i7.
> 
> Best regards
> Uwe

Thanks Uwe. I looked into cross testing but customizing the ARM version
of ArchLinux to our custom board is too much work at the moment.
Maybe I can reproduce it with other ARM boards like the Raspberry Pi or
the BeagleBone Black, for which working ArchLinux images already exist.

Michael: Do you have an idea what could lead to the SystemCallFilter
having no effect even though systemd shows +SECCOMP?

If it's working for you, we could still add seccomp support for systemd
in ptxdist and I have to figure out why it isn't working on my i.MX6
board.

I noticed just now that I did not have CONFIG_CHECKPOINT_RESTORE enabled
in my kernel when testing systemd with seccomp. I will repeat the tests
with that configuration set, maybe that's the culprit..

Thanks,
Clemens

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

      reply	other threads:[~2015-12-20 15:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-29 15:21 Clemens Gruber
2015-11-29 15:47 ` Uwe Kleine-König
2015-12-20 15:30   ` Clemens Gruber [this message]

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=20151220153003.GC25555@archie.tuxnet.lan \
    --to=clemens.gruber@pqgruber.com \
    --cc=ptxdist@pengutronix.de \
    /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