From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Michael Ellerman <mpe@ellerman.id.au>, linuxppc-dev@ozlabs.org
Cc: asolokha@kb.kras.ru, linux-kernel@vger.kernel.org, christian@brauner.io
Subject: Re: [PATCH v2] powerpc: Wire up clone3 syscall
Date: Wed, 31 Jul 2019 08:50:12 +1000 (AEST) [thread overview]
Message-ID: <45ysFx2Nxqz9sMr@ozlabs.org> (raw)
In-Reply-To: <20190724140259.23554-1-mpe@ellerman.id.au>
On Wed, 2019-07-24 at 14:02:59 UTC, Michael Ellerman wrote:
> Wire up the new clone3 syscall added in commit 7f192e3cd316 ("fork:
> add clone3").
>
> This requires a ppc_clone3 wrapper, in order to save the non-volatile
> GPRs before calling into the generic syscall code. Otherwise we hit
> the BUG_ON in CHECK_FULL_REGS in copy_thread().
>
> Lightly tested using Christian's test code on a Power8 LE VM.
>
> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Applied to powerpc fixes.
https://git.kernel.org/powerpc/c/cee3536d24a1d5db66b9f68c3ece0af128187ab4
cheers
prev parent reply other threads:[~2019-07-30 22:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 14:02 [PATCH v2] powerpc: Wire up clone3 syscall Michael Ellerman
2019-07-24 14:21 ` Christian Brauner
2019-07-30 22:50 ` Michael Ellerman [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=45ysFx2Nxqz9sMr@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=asolokha@kb.kras.ru \
--cc=christian@brauner.io \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mpe@ellerman.id.au \
/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).