From: "H. Peter Anvin" <hpa@linux.intel.com>
To: "Bryn M. Reeves" <bmr@redhat.com>
Cc: device-mapper development <dm-devel@redhat.com>,
"Kasatkin, Dmitry" <dmitry.kasatkin@intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [dm-devel] dmsetup fails on latest kernel
Date: Thu, 19 Jan 2012 11:58:22 -0800 [thread overview]
Message-ID: <4F1875DE.8010805@linux.intel.com> (raw)
In-Reply-To: <4F185BBC.1010607@redhat.com>
On 01/19/2012 10:06 AM, Bryn M. Reeves wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 01/19/2012 04:10 PM, Kasatkin, Dmitry wrote:
>> It seems "semget" is missing from:
>> arch/x86/syscalls/syscall_32.tbl But it presents in:
>> arch/x86/syscalls/syscall_64.tbl
>>
>> Is it a bug then?
>
> Maybe; I noticed that too but it's also missing in the old x86
> unistd_32.h.
>
> I thought Linux only provided the ipc(2) call - glibc sources seem to
> confirm that (sysdeps/unix/sysv/linux/semget.c).
>
> sys_sem* and friends are present in include/asm-generic/unistd.h so
> maybe these values just need to be propagated to syscall_32.tbl?
>
> Actually there's a bunch of SysV IPC calls defined in syscall_64.tbl
> that are not present in syscall_32.tbl:
>
> $ egrep 'shm|sem|msg[a-z]' arch/x86/syscalls/syscall_32.tbl
> $ egrep 'shm|sem|msg[a-z]' arch/x86/syscalls/syscall_64.tbl
> 29 64 shmget sys_shmget
> 30 64 shmat sys_shmat
> 31 64 shmctl sys_shmctl
> 64 64 semget sys_semget
> 65 64 semop sys_semop
> 66 64 semctl sys_semctl
> 67 64 shmdt sys_shmdt
> 68 64 msgget sys_msgget
> 69 64 msgsnd sys_msgsnd
> 70 64 msgrcv sys_msgrcv
> 71 64 msgctl sys_msgctl
> 220 64 semtimedop sys_semtimedop
>
> But sys_ipc is there:
>
> $ grep sys_ipc arch/x86/syscalls/syscall_32.tbl
> 117 i386 ipc sys_ipc sys32_ipc
>
No, the i386 ABI uses several system call multiplexes (sys_ipc,
sys_socketcall) which are deprecated for new ABIs. x86-64 and other new
ABIs use plain system calls. Thus, this is all as one should expect;
the right thing to do is to compare against the old 32-bit system call
table.
-hpa
next prev parent reply other threads:[~2012-01-19 19:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 13:02 dmsetup fails on latest kernel Kasatkin, Dmitry
2012-01-19 15:56 ` Kasatkin, Dmitry
2012-01-19 16:10 ` Kasatkin, Dmitry
2012-01-19 18:06 ` [dm-devel] " Bryn M. Reeves
2012-01-19 19:58 ` H. Peter Anvin [this message]
2012-01-19 19:05 ` Linus Torvalds
2012-01-19 19:58 ` H. Peter Anvin
2012-01-20 12:52 ` Kasatkin, Dmitry
2012-01-19 20:13 ` H. Peter Anvin
2012-01-19 20:17 ` Linus Torvalds
2012-01-19 20:30 ` H. Peter Anvin
2012-01-19 21:16 ` H. Peter Anvin
2012-01-20 13:35 ` Kasatkin, Dmitry
2012-01-20 14:45 ` H. Peter Anvin
2012-01-19 21:40 ` [tip:x86/urgent] x86, syscall: Need __ARCH_WANT_SYS_IPC for 32 bits tip-bot for H. Peter Anvin
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=4F1875DE.8010805@linux.intel.com \
--to=hpa@linux.intel.com \
--cc=bmr@redhat.com \
--cc=dm-devel@redhat.com \
--cc=dmitry.kasatkin@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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).