From: Michael Ellerman <mpe@ellerman.id.au>
To: Laurent Dufour <ldufour@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Cc: paulus@samba.org, linux-kernel@vger.kernel.org
Subject: Re: powerpc: Enabling sys_kcmp for CRIU
Date: Mon, 11 May 2015 20:31:15 +1000 (AEST) [thread overview]
Message-ID: <20150511103115.DFE85140187@ozlabs.org> (raw)
In-Reply-To: <1430839821-9259-1-git-send-email-ldufour@linux.vnet.ibm.com>
On Tue, 2015-05-05 at 15:30:21 UTC, Laurent Dufour wrote:
> The commit 8170a83f15ee ("powerpc: Wireup the kcmp syscall to sys_ni") has
> disabled the kcmp syscall for powerpc. This has been done due to the use
> of unsigned long parameters which may require a dedicated wrapper to handle
> 32bit process on top of 64bit kernel. However in the kcmp() case, the 2
> unsigned long parameters are currently only used to carry file descriptors
> from user space to the kernel. Since such a parameter is passed through
> register, and file descriptor doesn't need to get extended, there is,
> today, no need for a wrapper.
>
> In the case there will be a need to pass address in or out of this system
> call, then a wrapper could be required, it will then be to care of it.
>
> As today this is not the case, it is safe to enable kcmp() on powerpc.
That's mostly convincing. Though I see that s390 does have a compat wrapper,
i386 doesn't. So who knows what that means.
But, there's a selftest in tools/testing/selftests/kcmp. So can you run that as
32-bit and confirm it works? Then I'd be 100% convinced :)
cheers
next prev parent reply other threads:[~2015-05-11 10:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 15:30 [PATCH] powerpc: Enabling sys_kcmp for CRIU Laurent Dufour
2015-05-05 15:30 ` Laurent Dufour
2015-05-11 10:31 ` Michael Ellerman [this message]
2015-05-11 11:53 ` Laurent Dufour
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=20150511103115.DFE85140187@ozlabs.org \
--to=mpe@ellerman.id.au \
--cc=ldufour@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.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.
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.