From: Piotr Figiel <figiel@google.com>
To: Alexey Dobriyan <adobriyan@gmail.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Andrew Morton <akpm@linux-foundation.org>,
Kees Cook <keescook@chromium.org>,
Alexey Gladkov <gladkov.alexey@gmail.com>,
Michel Lespinasse <walken@google.com>,
Bernd Edlinger <bernd.edlinger@hotmail.de>,
Andrei Vagin <avagin@gmail.com>,
mathieu.desnoyers@efficios.com, viro@zeniv.linux.org.uk,
peterz@infradead.org, paulmck@kernel.org, boqun.feng@gmail.com
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
posk@google.com, kyurtsever@google.com, ckennelly@google.com,
pjt@google.com
Subject: Re: [PATCH v4] fs/proc: Expose RSEQ configuration
Date: Wed, 10 Mar 2021 20:08:10 +0100 [thread overview]
Message-ID: <YEkZGsc9L7qygDPJ@google.com> (raw)
In-Reply-To: <20210202173709.4104221-1-figiel@google.com>
On Tue, Feb 02, 2021 at 06:37:09PM +0100, Piotr Figiel wrote:
> For userspace checkpoint and restore (C/R) some way of getting process
> state containing RSEQ configuration is needed.
[...]
> To achieve above goals expose the RSEQ ABI address and the signature
> value with the new procfs file "/proc/<pid>/rseq".
For the record: this idea was dropped in favor of ptrace approach, as
discussed over separate mail thread with Mathieu Desnoyers and Peter
Zijlstra. The equivalent ptrace patch in its current version is here:
https://lore.kernel.org/lkml/20210226135156.1081606-1-figiel@google.com/
Best regards,
Piotr.
prev parent reply other threads:[~2021-03-10 19:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 17:37 [PATCH v4] fs/proc: Expose RSEQ configuration Piotr Figiel
2021-03-10 19:08 ` Piotr Figiel [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=YEkZGsc9L7qygDPJ@google.com \
--to=figiel@google.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=avagin@gmail.com \
--cc=bernd.edlinger@hotmail.de \
--cc=boqun.feng@gmail.com \
--cc=ckennelly@google.com \
--cc=ebiederm@xmission.com \
--cc=gladkov.alexey@gmail.com \
--cc=keescook@chromium.org \
--cc=kyurtsever@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=posk@google.com \
--cc=viro@zeniv.linux.org.uk \
--cc=walken@google.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;
as well as URLs for NNTP newsgroup(s).