Searched full:user (Results 1 – 25 of 978) sorted by relevance
12345678910>>...40
| /Documentation/admin-guide/sysctl/ |
| D | user.rst | 2 Documentation for /proc/sys/user/
12 /proc/sys/user.
16 per user per user namespace limits.
24 The creation of per user per user namespace objects are charged to
25 the user in the user namespace who created the object and
26 verified to be below the per user limit in that user namespace.
29 who created user namespaces the creation of the object happens
30 in (user namespaces can be nested) and verified to be below the per user
31 limits in the user namespaces of those users.
34 user namespace does not allow a user to escape their current limits.
[all …]
|
| /Documentation/admin-guide/LSM/ |
| D | SafeSetID.rst | 8 allowing a user to set up user namespace UID mappings.
14 to switch to a different user must be spawned with CAP_SETUID privileges.
16 user that have been explicitly given the CAP_SETUID runtime capability. It is
19 privileges opens up possible security holes since any user with access to the
24 tree of processes under non-root user(s) in the first place. Specifically,
25 since CAP_SETUID allows changing to any user on the system, including the root
26 user, it is an overpowered capability for what is needed in this scenario,
28 lesser-privileged user -- not elevate privileges. Unfortunately, there is no
29 generally feasible way in Linux to restrict the potential UIDs that a user can
30 switch to through setuid() beyond allowing a switch to any user on the system.
[all …]
|
| /Documentation/arm/ |
| D | sunxi.rst | 26 * User Manual
28 …http://dl.linux-sunxi.org/A10/A10%20User%20Manual%20-%20v1.20%20%282012-04-09%2c%20DECRYPTED%29.pdf
41 * User Manual
43 http://dl.linux-sunxi.org/A13/A13%20User%20Manual%20-%20v1.2%20%282013-01-08%29.pdf
57 * User Manual
59 http://dl.linux-sunxi.org/A20/A20%20User%20Manual%202013-03-22.pdf
67 * User Manual
69 http://dl.linux-sunxi.org/A23/A23%20User%20Manual%20V1.0%2020130830.pdf
78 * User Manual
80 …http://dl.linux-sunxi.org/A31/A3x_release_document/A31/IC/A31%20user%20manual%20V1.1%2020130630.pdf
[all …]
|
| /Documentation/powerpc/ |
| D | cxlflash.rst | 24 CXL provides a mechanism by which user space applications can
27 user space application direct access to Flash storage.
33 special path for user space access, and performing error recovery. It
44 user space with a special block library. This mode further
59 directly in each user I/O, but at the minimum is involved in the
60 initial setup before the user application is allowed to send requests
68 | 512 * 64 KB User MMIO |
70 | User Accessible |
90 access to the Flash from user space (without requiring a system call).
93 block library to enable this user space access. The driver supports
[all …]
|
| D | dscr.rst | 5 DSCR register in powerpc allows user to have some control of prefetch of data
10 user interface.
55 (D) User Space Instructions:
57 The DSCR register can be accessed in the user space using any of these
63 Accessing DSCR through privileged SPR number (0x11) from user space
67 Accessing DSCR through user level SPR (0x03) from user space will first
84 (3) ptrace interface (Explicitly set user DSCR value)
|
| /Documentation/admin-guide/namespaces/ |
| D | compatibility-list.rst | 5 This document contains the information about the problems user
13 - UTS IPC VFS PID User Net
19 User 2 2 X
33 2. Intentionally, two equal user IDs in different user namespaces
35 words, user 10 in one user namespace shouldn't have the same
36 access permissions to files, belonging to user 10 in another
40 from different user namespaces should not access the same IPC objects
|
| D | resource-control.rst | 7 of processes is allowed to switch user ids. With user namespaces
12 kernels that enable user namespaces, and it is further recommended
14 memory user's they don't trust to play nice can use.
|
| /Documentation/ABI/testing/ |
| D | sysfs-kernel-uids | 7 to set the cpu bandwidth a user is allowed. This is a
11 example would be, if User A has shares = 1024 and user
12 B has shares = 2048, User B will get twice the CPU
13 bandwidth user A will. For more details refer
|
| D | configfs-acpi | 14 This group contains the configuration for user defined ACPI
15 tables. The attributes of a user define table are:
17 aml - a binary attribute that the user can use to
22 successful the user must check the error code
|
| /Documentation/admin-guide/cgroup-v1/ |
| D | cpuacct.rst | 35 CPU time obtained by the cgroup into user and system times. Currently
38 user: Time spent by tasks of the cgroup in user mode.
41 user and system are in USER_HZ unit.
43 cpuacct controller uses percpu_counter interface to collect user and
46 - It is theoretically possible to see wrong values for user and system times.
49 - It is possible to see slightly outdated values for user and system times
|
| /Documentation/security/keys/ |
| D | ecryptfs.rst | 9 either in kernel space or in user space with a daemon called 'ecryptfsd'. In
11 using a key, the FEKEK, derived from a user prompted passphrase; in the latter
18 kernel key of the 'user' type, inserted in the user's session specific keyring
49 key-type:= 'trusted' | 'user'
56 'ecryptfs' and save it using a previously loaded user key "test"::
58 $ keyctl add encrypted 1000100010001000 "new ecryptfs user:test 64" @u
62 ecryptfs user:test 64 490045d4bfe48c99f0d465fbbbb79e7500da954178e2de0697
|
| /Documentation/filesystems/ |
| D | quota.txt | 9 and the second one hardlimit. A user can never exceed a hardlimit for any
10 resource (unless he has CAP_SYS_RESOURCE capability). User is allowed to exceed
12 period" or "grace time". When grace time is over, user is not able to allocate
23 When user exceeds a softlimit, runs out of grace time or reaches hardlimit,
26 when user is using a graphical desktop he usually cannot see the message.
45 - UID/GID (depends on quota type) of user / group whose limit
48 - UID of a user who caused the event
59 - four warnings are also defined for the event when user stops
|
| D | affs.txt | 33 The muFS (multi user File System) equivalents of the above file systems
42 system to uid or the uid of the current user, respectively.
94 - R maps to r for user, group and others. On directories, R implies x.
104 User id and group id will be used unless set[gu]id are given as mount
105 options. Since most of the Amiga file systems are single user systems
107 Amiga filesystem will be owned by the user who actually mounts the
114 - r permission will set R for user, group and others.
116 - w permission will set W and D for user, group and others.
118 - x permission of the user will set E for plain files.
123 Newly created files and directories will get the user and group ID
[all …]
|
| D | 9p.txt | 38 For Plan 9 From User Space applications (http://swtch.com/plan9)
40 mount -t 9p `namespace`/acme /mnt/9 -o trans=unix,uname=$USER
64 uname=name user name to attempt mount as on the remote server. The
65 server may override or ignore this value. Certain user
121 user = if a user tries to access a file on v9fs
123 attach command (Tattach) for that user.
125 <uid> = allows only user with uid=<uid> to access
128 operations as one user
148 There are user and developer mailing lists available through the v9fs project
159 For information on Plan 9 from User Space (Plan 9 applications and libraries
|
| /Documentation/virt/kvm/devices/ |
| D | vm.txt | 49 Allows user space to retrieve machine and kvm specific cpu related information:
67 Allows user space to retrieve or request to change cpu related information for a vcpu:
91 Allows user space to retrieve available cpu features. A feature is available if
105 Allows user space to retrieve or change enabled cpu features for all VCPUs of a
118 Allows user space to retrieve available cpu subfunctions without any filtering
154 Allows user space to retrieve or change cpu subfunctions to be indicated for
160 has not been disabled by user space (so the instruction to be queried is
180 Allows user space to set/get the TOD clock extension (u8) (superseded by
183 Parameters: address of a buffer in user space to store the data (u8) to
189 Allows user space to set/get bits 0-63 of the TOD clock register as defined in
[all …]
|
| /Documentation/firmware-guide/acpi/ |
| D | video_extension.rst | 16 Export a sysfs interface for user space to control backlight level
70 as a "brightness level" indicator. Thus from the user space perspective
74 Notify user space about hotkey event
79 i) For some laptops, when user presses the hotkey, a scancode will be
80 generated and sent to user space through the input device created by
82 following key code will appear to user space::
95 notify value it received and send the event to user space through the
108 Once user space tool receives this event, it can modify the backlight
116 not affect the sending of event to user space, they are always sent to user
|
| /Documentation/driver-api/ |
| D | ptp.rst | 9 presents a standardized method for developing PTP user space
14 drivers and a user space interface. The infrastructure supports a
25 - Period output signals configurable from user space
32 class driver handles all of the dealings with user space. The
43 PTP hardware clock user space API
47 registered clock. User space can use an open file descriptor from
52 User space programs may control the clock using standardized
54 ancillary clock features. User space can receive time stamped
|
| /Documentation/admin-guide/device-mapper/ |
| D | kcopyd.rst | 16 To start a copy job, the user must set up io_region structures to describe
28 To start the copy, the user calls kcopyd_copy(), passing in the client
39 When the copy completes, kcopyd will call the user's completion routine,
40 passing back the user's context pointer. It will also indicate if a read or
43 When a user is done with all their copy jobs, they should call
|
| /Documentation/dev-tools/ |
| D | gdb-kernel-debugging.rst | 74 scanning for modules in /home/user/linux/build
75 loading @0xffffffffa0020000: /home/user/linux/build/net/netfilter/xt_tcpudp.ko
76 loading @0xffffffffa0016000: /home/user/linux/build/net/netfilter/xt_pkttype.ko
77 loading @0xffffffffa0002000: /home/user/linux/build/net/netfilter/xt_limit.ko
78 loading @0xffffffffa00ca000: /home/user/linux/build/net/packet/af_packet.ko
79 loading @0xffffffffa003c000: /home/user/linux/build/fs/fuse/fuse.ko
81 loading @0xffffffffa0000000: /home/user/linux/build/drivers/ata/ata_generic.ko
97 loading @0xffffffffa0034000: /home/user/linux/build/lib/libcrc32c.ko
98 loading @0xffffffffa0050000: /home/user/linux/build/lib/lzo/lzo_compress.ko
99 loading @0xffffffffa006e000: /home/user/linux/build/lib/zlib_deflate/zlib_deflate.ko
[all …]
|
| /Documentation/driver-api/nvdimm/ |
| D | security.rst | 31 erase <keyid> - delete existing user encryption key.
34 master_erase <keyid> - delete existing user encryption key.
48 kernel API call during nvdimm unlock. It is up to the user to make sure that
49 all the keys are in the kernel user keyring for unlock.
61 retrieve the key from the kernel user keyring. This is the only time
64 relevant encrypted-keys into the kernel user keyring during the initramfs phase.
72 the kernel user keyring and reinjected as different (old) key. It's irrelevant
86 frozen by a user with root privelege.
94 in the kernel user keyring.
102 in the kernel user keyring.
[all …]
|
| /Documentation/vm/ |
| D | active_mm.rst | 28 user-level page tables at all, so when we do a context switch into an
33 doesn't need any user mappings - all kernel threads basically fall into
35 some amount of time they are not going to be interested in user space,
45 "stole" for such an anonymous user. For that, we have "tsk->active_mm",
62 Usually there is at least one real user, but it could be that the real
63 user exited on another CPU while a lazy user was still active, so you do
81 we have a user context", and is generally done by the page fault handler
|
| /Documentation/admin-guide/ |
| D | perf-security.rst | 13 generated by Perf tool user mode utility (Perf) [3]_ , [4]_ . The risk
25 2. User and kernel module paths and their load addresses with sizes,
38 RBP on x86_64), process user and kernel space memory addresses and
53 into two categories [6]_ : a) privileged processes (whose effective user
139 performance monitoring. Per-user per-cpu perf_event_mlock_kb [2]_
149 user or in kernel space can be monitored and captured for later
150 analysis. Per-user per-cpu perf_event_mlock_kb locking limit is
157 happened when executing either in user or in kernel space can be
158 monitored and captured for later analysis. Per-user per-cpu
164 system events happened when executing in user space only can be
[all …]
|
| /Documentation/admin-guide/pm/ |
| D | strategies.rst | 16 which user space code cannot be executed and the overall system activity is
18 kernel puts the system into one of these states when requested by user space
21 user space code can run. Because sleep states are global and the whole system
42 then it takes much less time and effort to start executing user space code than
50 Namely, if the user indicates that the system will not be in use going forward,
52 go into a sleep state at that point. On the other hand, if the user simply goes
54 use the working-state power management in case it becomes idle, because the user
|
| /Documentation/devicetree/bindings/sound/ |
| D | widgets.txt | 7 "template-wname", "user-supplied-wname"
12 The "user-supplied-wname" being the user specified widget name.
|
| /Documentation/networking/ |
| D | af_xdp.rst | 20 XDP programs to redirect frames to a memory buffer in a user-space
38 is simply an offset within the entire UMEM region. The user space
47 kernel has transmitted completely and can now be used again by user
72 user-space application can place an XSK at an arbitrary place in this
79 traffic to user space through the XSK.
84 together with the generic XDP support and copies out the data to user
88 data into user space.
118 user-space application.
124 TX. All rings are single-producer/single-consumer, so the user-space
140 calls and mmapped to user-space using the appropriate offset to mmap()
[all …]
|
12345678910>>...40