JM プロジェクトは、主に Linux 関連のマニュアルページの日本語ページを翻訳・公開しています。
... , posix_fadvise (2), pread64 (2), pwrite64 (2), readahead (2), sync_file_range (2), truncate64 (2) This does not affect syscalls that manually split and assemble 64-bit values such as _llseek (2), preadv (2), preadv2 (2), pwritev (2), and pwritev2 (2) ... all result, and the register used to signal an error. Arch/ABI Instruction System Ret Ret Error 備考 call # val val2 alpha callsys v0 v0 a4 a3 1, 6 arc trap0 r8 r0 - - arm/OABI swi NR - r0 - - 2 arm/EABI swi 0x0 r7 r0 r1 - arm64 svc #0 w8 x0 x1 - blac ... erH, the trap number controls the maximum number of arguments passed. A trap #0x10 can be used with only 0-argument system calls, a trap #0x11 can be used with 0- or 1-argument system calls, and so on up to trap #0x17 for 7-argument system calls. [5] ... ... system call has returned. (These are the same steps that are performed by syscall (2), which can be used to invoke system calls for which no wrapper function is provided.) Note: system calls indicate a failure by returning a negative error number to ... .x の不安定版のカーネル系列として開発された。) * Starting with kernel 2.6.0, the development model changed, and new system calls may appear in each 2.6.x release. In this case, the exact version number where the system call appeared is shown. This con ... た。 Linux 2.6.13 で追加され、2.6.16 で削除された。このシステムコールがユーザー空間から使える状態になったことはない。 System calls on removed ports Some system calls only ever existed on Linux architectures that have since been removed from the kernel: ... ... 成して (訳註: テストファイルを) 配置する。 オプション -v 詳細な出力。 -t secs 指定した実行時間 (単位: 秒) と負荷に基づいて、 calls を設定する。 -c calls 生成する NFS 呼び出しの総数 (デフォルトは 5000)。 -l load 1 秒当りの NFS 呼び出しを生成する負荷 (デフ ... 関連項目 ソースコード nhfsstone.c には、プログラムの詳細な操作を記述したコメントが書かれている。 エラーメッセージ illegal calls value コマンドラインで指定された -c フラグの後の calls 引き数が正の数でない。 illegal load value コマンドラインで指定された ... 合) や ファイルシステムがいっぱいである場合が多い。 bad mix format: unexpected EOF after 'nfs:' bad mix format: can't find 'calls' value bad mix format: unexpected EOF after 'calls' bad mix format: can't find %d op values bad mix format: unexpected EOF ... ... e is a chunk of arbitrary textual or binary data that was assigned using setxattr (2). If size is specified as zero, these calls return the current size of the named extended attribute (and leave value unchanged). This can be used to determine the siz ... d in a subsequent call. (But, bear in mind that there is a possibility that the attribute value may change between the two calls, so that it is still necessary to check the return status from the second call.) 返り値 On success, these calls return a n ... ... e is a chunk of arbitrary textual or binary data that was assigned using setxattr (2). If size is specified as zero, these calls return the current size of the named extended attribute (and leave value unchanged). This can be used to determine the siz ... d in a subsequent call. (But, bear in mind that there is a possibility that the attribute value may change between the two calls, so that it is still necessary to check the return status from the second call.) 返り値 On success, these calls return a n ... ... e is a chunk of arbitrary textual or binary data that was assigned using setxattr (2). If size is specified as zero, these calls return the current size of the named extended attribute (and leave value unchanged). This can be used to determine the siz ... d in a subsequent call. (But, bear in mind that there is a possibility that the attribute value may change between the two calls, so that it is still necessary to check the return status from the second call.) 返り値 On success, these calls return a n ... ... 32, socketcall () was historically the only entry point for the sockets API. However, starting in Linux 4.3, direct system calls are provided on x86-32 for the sockets API. This facilitates the creation of seccomp (2) filters that filter sockets syste ... m calls (for new user-space binaries that are compiled to use the new entry points) and also provides a (very) small performance i ... ... linux-gate.so.1 x86-64 linux-vdso.so.1 x86/x32 linux-vdso.so.1 strace (1), seccomp (2), and the vDSO When tracing systems calls with strace (1), symbols (system calls) that are exported by the vDSO will not appear in the trace output. Those system ca ... all_via_epc LINUX_2.5 The Itanium port is somewhat tricky. In addition to the vDSO above, it also has "light-weight system calls" (also known as "fast syscalls" or "fsys"). You can invoke these via the __kernel_syscall_via_epc vDSO helper. The system ... の機能をユーザー空間に渡す有効な方法であると認識されるようになり、 現在の形の vDSO という形に見直しが行われた。 関連項目 syscalls (2), getauxval (3), proc (5) Linux のソースコードツリーのドキュメント、例、ソースコード: Documentation/ABI/stable/vdso Doc ... ... intended to be used for any kind of security purpose, neither to fully sandbox a process nor to restrict filesystem system calls. In the past, chroot () has been used by daemons to restrict themselves prior to passing paths supplied by untrusted users ... to system calls such as open (2). However, if a folder is moved out of the chroot directory, an attacker can exploit that to get out of th ... ... ndler function. 4. When the signal handler returns, control passes to the signal trampoline code. 5. The signal trampoline calls sigreturn (2), a system call that uses the information in the stack frame created in step 1 to restore the thread to its s ... me signals required the widening of the signal set structure ( sigset_t ) from 32 to 64 bits. Consequently, various system calls were superseded by new system calls that supported the larger signal sets. The old and new system calls are as follows: Li ... flag was used; otherwise the call fails with the error EINTR : * read (2), readv (2), write (2), writev (2), and ioctl (2) calls on "slow" devices. A "slow" device is one where the I/O call may block for an indefinite time, for example, a terminal, pi ... 日本語の文書やマニュアルを配布している個人/プロジェクトへのリンクです。