Hi,
here is a first draft to describe prctl extension and new
kcmp syscall. So I woule _really_ appreciate any feedback.
Cyrill
NAME
kcmp - compare if two processes do share a particular kernel resource
SYNOPSIS
#define GNU SOURCE /* See feature test macros(7) */
#include <unistd.h>
#include <linux/kcmp.h>
#include <sys/syscall.h> /* For SYS xxx definitions */
int syscall( NR kcmp, pid1, pid2, type, idx1, idx2);
DESCRIPTION
kcmp() allows to find out if two processes identified by pid1
and pid2 do share kernel resources such as virtual memory, file
The comparison type is one of the following
KCMP FILE to compare two file descriptors specified by idx1 and idx2
KCMP VM to compare whether processes do share virtual memory
KCMP FILES to compare whether processes do share share the file descriptor table
KCMP FS to compare whether processes do share the file system information
KCMP SIGHAND to compare whether processes do share a signal handlers table
KCMP IO to compare whether processes do share I/O context
KCMP SYSVSEM to compare whether processes do share a single list of System V
semaphore undo values
RETURN VALUE
kcmp was designed to return values suitable for sorting. This is particularly
handy when one have to compare a large number
The return value is merely a result of simple arithmetic comparison of kernel
pointers (when kernel compares resources, it us
The easiest way to explain is to consider an example. Lets say v1 and v2
are the addresses of appropriate resources, then the return value is one
of the following
0 - v1 is equal to v2 , in other words we have a shared resource here
1 - v1 is greater than v2
2 - v1 is less than v2
3 - v1 is not equal to v2 , but ordering information is unavailble.
On error, -1 is returned, and errno is set appropriately.
CONFORMING TO
kcmp() is Linux specific and should not be used in programs intended to
be portable.
SEE ALSO
clone(2)
Signed-off-by: Cyrill Gorcunov <[email protected]>
CC: "Eric W. Biederman" <[email protected]>
CC: "H. Peter Anvin" <[email protected]>
CC: Pavel Emelyanov <[email protected]>
---
man2/kcmp.2 | 105 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
1 files changed, 105 insertions(+), 0 deletions(-)
create mode 100644 man2/kcmp.2
diff --git a/man2/kcmp.2 b/man2/kcmp.2
new file mode 100644
index 0000000..de07367
--- /dev/null
+++ b/man2/kcmp.2
@@ -0,0 +1,105 @@
+.TH KCMP 2 2012-02-01 "Linux" "Linux Programmer's Manual"
+
+.SH NAME
+kcmp \- compare if two processes do share a particular kernel resource
+
+.SH SYNOPSIS
+.nf
+.BR "#define _GNU_SOURCE" " /* See feature_test_macros(7) */"
+.B #include <unistd.h>
+.B #include <linux/kcmp.h>
+.BR "#include <sys/syscall.h> " "/* For SYS_xxx definitions */"
+
+.BI "int syscall(__NR_kcmp, pid1, pid2, type, idx1, idx2);"
+.fi
+
+.SH DESCRIPTION
+
+.BR kcmp ()
+allows to find out if two processes identified by
+.I pid1
+and
+.I pid2
+do share kernel resources such as virtual memory, file descriptors,
+file system etc.
+
+The comparison
+.I type
+is one of the following
+
+.BR KCMP_FILE
+to compare two file descriptors specified by
+.I idx1
+and
+.I idx2
+
+.BR KCMP_VM
+to compare whether processes do share virtual memory
+
+.BR KCMP_FILES
+to compare whether processes do share share the file descriptor table
+
+.BR KCMP_FS
+to compare whether processes do share the file system information
+
+.BR KCMP_SIGHAND
+to compare whether processes do share a signal handlers table
+
+.BR KCMP_IO
+to compare whether processes do share I/O context
+
+.BR KCMP_SYSVSEM
+to compare whether processes do share a single list of
+System V semaphore undo values
+
+.SH "RETURN VALUE"
+.B kcmp
+was designed to return values suitable for sorting.
+This is particularly handy when one have to compare
+a large number of file descriptors.
+
+The return value is merely a result of simple arithmetic comparison
+of kernel pointers (when kernel compares resources, it uses their
+memory addresses).
+
+The easiest way to explain is to consider an example.
+Lets say
+.I v1
+and
+.I v2
+are the addresses of appropriate resources, then the return value
+is one of the following
+
+.B 0
+\-
+.I v1
+is equal to
+.I v2
+, in other words we have a shared resource here
+
+.B 1
+\-
+.I v1
+is greater than
+.I v2
+
+.B 2
+\-
+.I v1
+is less than
+.I v2
+
+.B 3
+\-
+.I v1
+is not equal to
+.I v2
+, but ordering information is unavailble.
+
+On error, \-1 is returned, and errno is set appropriately.
+
+.SH "CONFORMING TO"
+.BR kcmp ()
+is Linux specific and should not be used in programs intended to be portable.
+.SH "SEE ALSO"
+.BR clone (2)
--
1.7.7.6
Signed-off-by: Cyrill Gorcunov <[email protected]>
CC: Tejun Heo <[email protected]>
CC: Pavel Emelyanov <[email protected]>
---
man2/prctl.2 | 104 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
1 files changed, 104 insertions(+), 0 deletions(-)
diff --git a/man2/prctl.2 b/man2/prctl.2
index effad2a..4d6244f 100644
--- a/man2/prctl.2
+++ b/man2/prctl.2
@@ -378,6 +378,110 @@ Return the current per-process machine check kill policy.
All unused
.BR prctl ()
arguments must be zero.
+.TP
+.BR PR_SET_MM " (since Linux 3.3)"
+Allows a user to modify certain kernel memory map descriptor fields
+of the calling process.
+Usually these fields are set by the kernel and dynamic loader (see
+.BR ld.so (8)
+for more information) and a regular application should not use this feature.
+Still there are cases such as self-modifying programs, where a program might
+find it useful to change its own memory map.
+The kernel must be built with
+.BR CONFIG_CHECKPOINT_RESTORE
+option turned on, otherwise this feature will not be accessible
+from a user space level.
+The calling process must have
+.BR CAP_SYS_ADMIN
+(see
+.BR capabilities (7)
+for details) capability granted.
+The value in
+.I arg2
+is one of the options below, while
+.I arg3
+provides a new value for this option.
+
+.BR PR_SET_MM_START_CODE
+to set the address above which program text can run.
+The corresponding memory area must be readable and executable,
+but not writable or shareable (see
+.BR mprotect (2)
+and
+.BR mmap (2)
+for more information).
+
+.BR PR_SET_MM_END_CODE
+to set the address below which program text can run.
+The corresponding memory area must be readable and executable,
+but not writable or shareable.
+
+.BR PR_SET_MM_START_DATA
+to set the address above which program data+bss is placed.
+The corresponding memory area must be readable and writable,
+but not executable or shareable.
+
+.B PR_SET_MM_END_DATA
+to set the address below which program data+bss is placed.
+The corresponding memory area must be readable and writable,
+but not executable or shareable.
+
+.BR PR_SET_MM_START_STACK
+to set the start address of the stack.
+The corresponding memory area must be readable and writable.
+
+.BR PR_SET_MM_START_BRK
+to set the address above which program heap can be expanded with
+.BR brk (2)
+call.
+The address must not be greater than ending address of
+the current program data segment, neither it may exceed
+resource limit for data (see
+.BR setrlimit (2)
+for more information).
+
+.BR PR_SET_MM_BRK
+to set the current
+.BR brk (2)
+value.
+The requirements for address are the same as for
+.BR PR_SET_MM_START_BRK
+option.
+
+.BR PR_SET_MM_ARG_START
+to set the address above which program command line is placed.
+
+.BR PR_SET_MM_ARG_END
+to set the address below which program command line is placed.
+
+.BR PR_SET_MM_ENV_START
+to set the address above which program environment is placed.
+
+.BR PR_SET_MM_ENV_END
+to set the address below which program environment is placed.
+
+The address passed with
+.BR PR_SET_MM_ARG_START ,
+.BR PR_SET_MM_ARG_END ,
+.BR PR_SET_MM_ENV_START ,
+.BR PR_SET_MM_ENV_END ,
+should belong to a process stack area, thus corresponding memory area
+must be readable, writable and (depending on the kernel
+configuration) has
+.BR MAP_GROWSDOWN
+attribute set (see
+.BR mmap (2)
+for details).
+
+.BR PR_SET_MM_AUXV
+to set a new auxiliary vector.
+The
+.I arg3
+argument should provide the address of the vector.
+The
+.I arg4
+is the size of the vector.
+.\"
.SH "RETURN VALUE"
On success,
.BR PR_GET_DUMPABLE ,
--
1.7.7.6
On Wed, Feb 29, 2012 at 04:23:17PM +0400, Cyrill Gorcunov wrote:
>
> The easiest way to explain is to consider an example. Lets say v1 and v2
> are the addresses of appropriate resources, then the return value is one
> of the following
>
> 0 - v1 is equal to v2 , in other words we have a shared resource here
>
> 1 - v1 is greater than v2
>
> 2 - v1 is less than v2
1 and 2 should be swapped here, I'll update (this nit grow from text tossing,
so don't pay attention on it).
Cyrill
On Wed, Feb 29, 2012 at 04:34:08PM +0400, Cyrill Gorcunov wrote:
> 1 and 2 should be swapped here, I'll update (this nit grow from text tossing,
> so don't pay attention on it).
>
Updated version below.
Cyrill
---
From: Cyrill Gorcunov <[email protected]>
Date: Wed, 29 Feb 2012 16:40:13 +0400
Subject: [PATCH 2/2] Add kcmp.2 manpage
NAME
kcmp - compare if two processes do share a particular kernel resource
SYNOPSIS
#define GNU SOURCE /* See feature test macros(7) */
#include <unistd.h>
#include <linux/kcmp.h>
#include <sys/syscall.h> /* For SYS xxx definitions */
int syscall( NR kcmp, pid1, pid2, type, idx1, idx2);
DESCRIPTION
kcmp() allows to find out if two processes identified by pid1
and pid2 do share kernel resources such as virtual memory, file
The comparison type is one of the following
KCMP FILE to compare two file descriptors specified by idx1 and idx2
KCMP VM to compare whether processes do share virtual memory
KCMP FILES to compare whether processes do share share the file descriptor table
KCMP FS to compare whether processes do share the file system information
KCMP SIGHAND to compare whether processes do share a signal handlers table
KCMP IO to compare whether processes do share I/O context
KCMP SYSVSEM to compare whether processes do share a single list of System V
semaphore undo values
RETURN VALUE
kcmp was designed to return values suitable for sorting. This is particularly
handy when one have to compare a large number
The return value is merely a result of simple arithmetic comparison of kernel
pointers (when kernel compares resources, it us
The easiest way to explain is to consider an example. Lets say v1 and v2
are the addresses of appropriate resources, then the return value is one
of the following
0 - v1 is equal to v2 , in other words we have a shared resource here
1 - v1 is less than v2
2 - v1 is greater than v2
3 - v1 is not equal to v2 , but ordering information is unavailble.
On error, -1 is returned, and errno is set appropriately.
CONFORMING TO
kcmp() is Linux specific and should not be used in programs intended to
be portable.
SEE ALSO
clone(2)
Signed-off-by: Cyrill Gorcunov <[email protected]>
CC: "Eric W. Biederman" <[email protected]>
CC: "H. Peter Anvin" <[email protected]>
CC: Pavel Emelyanov <[email protected]>
---
man2/kcmp.2 | 105 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
1 files changed, 105 insertions(+), 0 deletions(-)
create mode 100644 man2/kcmp.2
diff --git a/man2/kcmp.2 b/man2/kcmp.2
new file mode 100644
index 0000000..de68109
--- /dev/null
+++ b/man2/kcmp.2
@@ -0,0 +1,105 @@
+.TH KCMP 2 2012-02-01 "Linux" "Linux Programmer's Manual"
+
+.SH NAME
+kcmp \- compare if two processes do share a particular kernel resource
+
+.SH SYNOPSIS
+.nf
+.BR "#define _GNU_SOURCE" " /* See feature_test_macros(7) */"
+.B #include <unistd.h>
+.B #include <linux/kcmp.h>
+.BR "#include <sys/syscall.h> " "/* For SYS_xxx definitions */"
+
+.BI "int syscall(__NR_kcmp, pid1, pid2, type, idx1, idx2);"
+.fi
+
+.SH DESCRIPTION
+
+.BR kcmp ()
+allows to find out if two processes identified by
+.I pid1
+and
+.I pid2
+do share kernel resources such as virtual memory, file descriptors,
+file system etc.
+
+The comparison
+.I type
+is one of the following
+
+.BR KCMP_FILE
+to compare two file descriptors specified by
+.I idx1
+and
+.I idx2
+
+.BR KCMP_VM
+to compare whether processes do share virtual memory
+
+.BR KCMP_FILES
+to compare whether processes do share share the file descriptor table
+
+.BR KCMP_FS
+to compare whether processes do share the file system information
+
+.BR KCMP_SIGHAND
+to compare whether processes do share a signal handlers table
+
+.BR KCMP_IO
+to compare whether processes do share I/O context
+
+.BR KCMP_SYSVSEM
+to compare whether processes do share a single list of
+System V semaphore undo values
+
+.SH "RETURN VALUE"
+.B kcmp
+was designed to return values suitable for sorting.
+This is particularly handy when one have to compare
+a large number of file descriptors.
+
+The return value is merely a result of simple arithmetic comparison
+of kernel pointers (when kernel compares resources, it uses their
+memory addresses).
+
+The easiest way to explain is to consider an example.
+Lets say
+.I v1
+and
+.I v2
+are the addresses of appropriate resources, then the return value
+is one of the following
+
+.B 0
+\-
+.I v1
+is equal to
+.I v2
+, in other words we have a shared resource here
+
+.B 1
+\-
+.I v1
+is less than
+.I v2
+
+.B 2
+\-
+.I v1
+is greater than
+.I v2
+
+.B 3
+\-
+.I v1
+is not equal to
+.I v2
+, but ordering information is unavailble.
+
+On error, \-1 is returned, and errno is set appropriately.
+
+.SH "CONFORMING TO"
+.BR kcmp ()
+is Linux specific and should not be used in programs intended to be portable.
+.SH "SEE ALSO"
+.BR clone (2)
--
1.7.7.6