2017-11-01 14:08:43 +00:00
|
|
|
/* SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note */
|
2009-05-13 22:56:26 +00:00
|
|
|
#ifndef __ASM_GENERIC_SHMBUF_H
|
|
|
|
|
#define __ASM_GENERIC_SHMBUF_H
|
|
|
|
|
|
|
|
|
|
#include <asm/bitsperlong.h>
|
2022-02-10 02:11:25 +00:00
|
|
|
#include <asm/ipcbuf.h>
|
|
|
|
|
#include <asm/posix_types.h>
|
2009-05-13 22:56:26 +00:00
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* The shmid64_ds structure for x86 architecture.
|
|
|
|
|
* Note extra padding because this structure is passed back and forth
|
|
|
|
|
* between kernel and user space.
|
|
|
|
|
*
|
|
|
|
|
* shmid64_ds was originally meant to be architecture specific, but
|
|
|
|
|
* everyone just ended up making identical copies without specific
|
|
|
|
|
* optimizations, so we may just as well all use the same one.
|
|
|
|
|
*
|
2019-11-04 20:17:26 +00:00
|
|
|
* 64 bit architectures use a 64-bit long time field here, while
|
|
|
|
|
* 32 bit architectures have a pair of unsigned long values.
|
|
|
|
|
* On big-endian systems, the lower half is in the wrong place.
|
2009-05-13 22:56:26 +00:00
|
|
|
*
|
|
|
|
|
*
|
|
|
|
|
* Pad space is left for:
|
|
|
|
|
* - 2 miscellaneous 32-bit values
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
struct shmid64_ds {
|
|
|
|
|
struct ipc64_perm shm_perm; /* operation perms */
|
2022-02-10 02:11:25 +00:00
|
|
|
__kernel_size_t shm_segsz; /* size of segment (bytes) */
|
y2038: asm-generic: Extend sysvipc data structures
Most architectures now use the asm-generic copy of the sysvipc data
structures (msqid64_ds, semid64_ds, shmid64_ds), which use 32-bit
__kernel_time_t on 32-bit architectures but have padding behind them to
allow extending the type to 64-bit.
Unfortunately, that fails on all big-endian architectures, which have the
padding on the wrong side. As so many of them get it wrong, we decided to
not bother even trying to fix it up when we introduced the asm-generic
copy. Instead we always use the padding word now to provide the upper
32 bits of the seconds value, regardless of the endianess.
A libc implementation on a typical big-endian system can deal with
this by providing its own copy of the structure definition to user
space, and swapping the two 32-bit words before returning from the
semctl/shmctl/msgctl system calls.
Note that msqid64_ds and shmid64_ds were broken on x32 since commit
f4b4aae18288 ("x86/headers/uapi: Fix __BITS_PER_LONG value for x32
builds"). I have sent a separate fix for that, but as we no longer
have to worry about x32 here, I no longer worry about x32 here and
use 'unsigned long' instead of __kernel_ulong_t.
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
2015-05-05 21:13:15 +00:00
|
|
|
#if __BITS_PER_LONG == 64
|
2019-11-04 20:17:26 +00:00
|
|
|
long shm_atime; /* last attach time */
|
|
|
|
|
long shm_dtime; /* last detach time */
|
|
|
|
|
long shm_ctime; /* last change time */
|
y2038: asm-generic: Extend sysvipc data structures
Most architectures now use the asm-generic copy of the sysvipc data
structures (msqid64_ds, semid64_ds, shmid64_ds), which use 32-bit
__kernel_time_t on 32-bit architectures but have padding behind them to
allow extending the type to 64-bit.
Unfortunately, that fails on all big-endian architectures, which have the
padding on the wrong side. As so many of them get it wrong, we decided to
not bother even trying to fix it up when we introduced the asm-generic
copy. Instead we always use the padding word now to provide the upper
32 bits of the seconds value, regardless of the endianess.
A libc implementation on a typical big-endian system can deal with
this by providing its own copy of the structure definition to user
space, and swapping the two 32-bit words before returning from the
semctl/shmctl/msgctl system calls.
Note that msqid64_ds and shmid64_ds were broken on x32 since commit
f4b4aae18288 ("x86/headers/uapi: Fix __BITS_PER_LONG value for x32
builds"). I have sent a separate fix for that, but as we no longer
have to worry about x32 here, I no longer worry about x32 here and
use 'unsigned long' instead of __kernel_ulong_t.
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
2015-05-05 21:13:15 +00:00
|
|
|
#else
|
|
|
|
|
unsigned long shm_atime; /* last attach time */
|
|
|
|
|
unsigned long shm_atime_high;
|
|
|
|
|
unsigned long shm_dtime; /* last detach time */
|
|
|
|
|
unsigned long shm_dtime_high;
|
|
|
|
|
unsigned long shm_ctime; /* last change time */
|
|
|
|
|
unsigned long shm_ctime_high;
|
2009-05-13 22:56:26 +00:00
|
|
|
#endif
|
|
|
|
|
__kernel_pid_t shm_cpid; /* pid of creator */
|
|
|
|
|
__kernel_pid_t shm_lpid; /* pid of last operator */
|
y2038: asm-generic: Extend sysvipc data structures
Most architectures now use the asm-generic copy of the sysvipc data
structures (msqid64_ds, semid64_ds, shmid64_ds), which use 32-bit
__kernel_time_t on 32-bit architectures but have padding behind them to
allow extending the type to 64-bit.
Unfortunately, that fails on all big-endian architectures, which have the
padding on the wrong side. As so many of them get it wrong, we decided to
not bother even trying to fix it up when we introduced the asm-generic
copy. Instead we always use the padding word now to provide the upper
32 bits of the seconds value, regardless of the endianess.
A libc implementation on a typical big-endian system can deal with
this by providing its own copy of the structure definition to user
space, and swapping the two 32-bit words before returning from the
semctl/shmctl/msgctl system calls.
Note that msqid64_ds and shmid64_ds were broken on x32 since commit
f4b4aae18288 ("x86/headers/uapi: Fix __BITS_PER_LONG value for x32
builds"). I have sent a separate fix for that, but as we no longer
have to worry about x32 here, I no longer worry about x32 here and
use 'unsigned long' instead of __kernel_ulong_t.
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
2015-05-05 21:13:15 +00:00
|
|
|
unsigned long shm_nattch; /* no. of current attaches */
|
|
|
|
|
unsigned long __unused4;
|
|
|
|
|
unsigned long __unused5;
|
2009-05-13 22:56:26 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
struct shminfo64 {
|
y2038: asm-generic: Extend sysvipc data structures
Most architectures now use the asm-generic copy of the sysvipc data
structures (msqid64_ds, semid64_ds, shmid64_ds), which use 32-bit
__kernel_time_t on 32-bit architectures but have padding behind them to
allow extending the type to 64-bit.
Unfortunately, that fails on all big-endian architectures, which have the
padding on the wrong side. As so many of them get it wrong, we decided to
not bother even trying to fix it up when we introduced the asm-generic
copy. Instead we always use the padding word now to provide the upper
32 bits of the seconds value, regardless of the endianess.
A libc implementation on a typical big-endian system can deal with
this by providing its own copy of the structure definition to user
space, and swapping the two 32-bit words before returning from the
semctl/shmctl/msgctl system calls.
Note that msqid64_ds and shmid64_ds were broken on x32 since commit
f4b4aae18288 ("x86/headers/uapi: Fix __BITS_PER_LONG value for x32
builds"). I have sent a separate fix for that, but as we no longer
have to worry about x32 here, I no longer worry about x32 here and
use 'unsigned long' instead of __kernel_ulong_t.
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
2015-05-05 21:13:15 +00:00
|
|
|
unsigned long shmmax;
|
|
|
|
|
unsigned long shmmin;
|
|
|
|
|
unsigned long shmmni;
|
|
|
|
|
unsigned long shmseg;
|
|
|
|
|
unsigned long shmall;
|
|
|
|
|
unsigned long __unused1;
|
|
|
|
|
unsigned long __unused2;
|
|
|
|
|
unsigned long __unused3;
|
|
|
|
|
unsigned long __unused4;
|
2009-05-13 22:56:26 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
#endif /* __ASM_GENERIC_SHMBUF_H */
|
