From: "H. Peter Anvin" <hpa@zytor.com>
To: Glauber Costa <glommer@parallels.com>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
gorcunov@openvz.org, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org, ebiederm@xmission.com,
xemul@openvz.org, xemul@parallels.com, avagin@openvz.org,
kosaki.motohiro@gmail.com, mingo@elte.hu, tglx@linutronix.de,
andi@firstfloor.org, tj@kernel.org, matthltc@us.ibm.com,
penberg@kernel.org, eric.dumazet@gmail.com, segoon@openwall.com,
adobriyan@gmail.com, Valdis.Kletnieks@vt.edu
Subject: Re: [RFC c/r 2/4] [RFC] syscalls, x86: Add __NR_kcmp syscall v7
Date: Fri, 27 Jan 2012 12:37:13 -0800 [thread overview]
Message-ID: <4F230AF9.1010104@zytor.com> (raw)
In-Reply-To: <4F230A40.8000203@parallels.com>
On 01/27/2012 12:34 PM, Glauber Costa wrote:
>>> + case KCMP_SYSVSEM:
>>> +#ifdef CONFIG_SYSVIPC
>>> + ret = kcmp_ptr((long)task1->sysvsem.undo_list,
>>> + (long)task2->sysvsem.undo_list,
>>> + KCMP_SYSVSEM);
>>> +#else
>>> + ret = -EINVAL;
>>
>> ENOTSUP is better, I think. because of, EINVAL implicitly mean _caller_ is wrong.
>> but in this case, it is not bad. only the kernel doesn't have enough feature.
>>
>
> Isn't it usually the case for ENOSYS, then ?
>
ENOSYS means "no such system call". That would apply if the kcmp system
call itself did not exist.
-hpa
next prev parent reply other threads:[~2012-01-27 20:38 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 17:53 [RFC c/r 0/4] [RFC c/r 0/@total@] A pile in c/r sake Cyrill Gorcunov
2012-01-27 17:53 ` [RFC c/r 1/4] fs, proc: Introduce /proc/<pid>/task/<tid>/children entry v9 Cyrill Gorcunov
2012-01-27 17:53 ` [RFC c/r 2/4] [RFC] syscalls, x86: Add __NR_kcmp syscall v7 Cyrill Gorcunov
2012-01-27 18:05 ` H. Peter Anvin
2012-01-27 18:11 ` Cyrill Gorcunov
2012-01-27 18:15 ` Andi Kleen
2012-01-27 18:24 ` Cyrill Gorcunov
2012-01-27 18:30 ` H. Peter Anvin
2012-01-28 17:19 ` Michael Kerrisk
2012-01-28 17:34 ` Cyrill Gorcunov
2012-01-28 17:36 ` Cyrill Gorcunov
2012-01-27 18:31 ` Andi Kleen
2012-01-27 18:40 ` Cyrill Gorcunov
2012-01-27 19:40 ` Andi Kleen
2012-01-27 20:55 ` Eric W. Biederman
2012-01-27 18:40 ` Eric W. Biederman
2012-01-27 18:45 ` Cyrill Gorcunov
2012-01-27 19:10 ` Cyrill Gorcunov
2012-01-27 19:37 ` Vasiliy Kulikov
2012-01-27 19:59 ` hpanvin@gmail.com
2012-01-27 20:07 ` Cyrill Gorcunov
2012-01-27 20:19 ` KOSAKI Motohiro
2012-01-27 20:33 ` Eric W. Biederman
2012-01-27 20:50 ` Cyrill Gorcunov
2012-01-27 21:19 ` Eric W. Biederman
2012-01-27 20:34 ` Glauber Costa
2012-01-27 20:37 ` H. Peter Anvin [this message]
2012-01-27 20:47 ` Cyrill Gorcunov
2012-01-27 17:53 ` [RFC c/r 3/4] c/r: procfs: add arg_start/end, env_start/end and exit_code members to /proc/$pid/stat Cyrill Gorcunov
2012-01-27 18:29 ` Kees Cook
2012-01-27 20:00 ` KOSAKI Motohiro
2012-01-27 20:10 ` Cyrill Gorcunov
2012-01-27 17:53 ` [RFC c/r 4/4] c/r: prctl: Extend PR_SET_MM to set up more mm_struct entries Cyrill Gorcunov
2012-01-27 18:37 ` Kees Cook
2012-01-27 18:43 ` Cyrill Gorcunov
2012-01-27 20:31 ` KOSAKI Motohiro
2012-01-27 20:28 ` KOSAKI Motohiro
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=4F230AF9.1010104@zytor.com \
--to=hpa@zytor.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=avagin@openvz.org \
--cc=ebiederm@xmission.com \
--cc=eric.dumazet@gmail.com \
--cc=glommer@parallels.com \
--cc=gorcunov@openvz.org \
--cc=kosaki.motohiro@gmail.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthltc@us.ibm.com \
--cc=mingo@elte.hu \
--cc=penberg@kernel.org \
--cc=segoon@openwall.com \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=xemul@openvz.org \
--cc=xemul@parallels.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
Powered by JetHome