From: Andreas Schwab <schwab@linux-m68k.org>
To: Carlos O'Donell via Libc-alpha <libc-alpha@sourceware.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Zack Weinberg <zackw@panix.com>, Cyril Hrubis <chrubis@suse.cz>,
Carlos O'Donell <carlos@redhat.com>,
Andrei Vagin <avagin@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Dmitry Safonov <dima@arista.com>
Subject: Re: [Y2038][time namespaces] Question regarding CLOCK_REALTIME support plans in Linux time namespaces
Date: Thu, 26 Nov 2020 09:21:55 +0100 [thread overview]
Message-ID: <87mtz41qak.fsf@igel.home> (raw)
In-Reply-To: <1d3d00ac-c7a0-7168-0450-8a0e1499ea2b@redhat.com> (Carlos O'Donell via Libc-alpha's message of "Wed, 25 Nov 2020 22:05:30 -0500")
On Nov 25 2020, Carlos O'Donell via Libc-alpha wrote:
> We might write a syscall interception framework using seccomp
> and SECCOMP_RET_TRACE, but that involves ptrace'ing the process
> under test, and is equivalent to a micro-sandbox. I'm not against
> that idea for testing; we would test what we ship.
seccomp and ptrace does not work with qemu linux-user.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2020-11-26 8:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 10:02 [Y2038][time namespaces] Question regarding CLOCK_REALTIME support plans in Linux time namespaces Lukasz Majewski
2020-10-30 13:08 ` Thomas Gleixner
2020-10-30 15:43 ` Lukasz Majewski
2020-10-30 13:58 ` Cyril Hrubis
2020-10-30 14:02 ` Zack Weinberg
2020-10-30 15:10 ` Thomas Gleixner
2020-10-30 16:58 ` Carlos O'Donell
2020-10-30 20:06 ` Thomas Gleixner
2020-10-30 22:19 ` Carlos O'Donell
2020-10-31 1:38 ` Thomas Gleixner
2020-11-03 12:43 ` Cyril Hrubis
2020-11-05 17:25 ` Carlos O'Donell
2020-11-07 0:47 ` Thomas Gleixner
2020-11-19 18:37 ` Carlos O'Donell
2020-11-20 0:14 ` Thomas Gleixner
2020-11-25 17:06 ` Petr Špaček
2020-11-25 20:37 ` Carlos O'Donell
2020-11-26 0:17 ` Thomas Gleixner
2020-11-26 3:05 ` Carlos O'Donell
2020-11-26 8:21 ` Andreas Schwab [this message]
2020-11-14 10:25 ` Pavel Machek
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=87mtz41qak.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=avagin@gmail.com \
--cc=carlos@redhat.com \
--cc=chrubis@suse.cz \
--cc=dima@arista.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=zackw@panix.com \
/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