Searched full:user (Results 1 – 25 of 1329) sorted by relevance
12345678910>>...54
| /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/arch/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/admin-guide/LSM/ |
| D | SafeSetID.rst | 8 allowing a user to set up user namespace UID/GID 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/arch/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/misc-devices/ |
| D | uacce.rst | 6 Uacce (Unified/User-space-access-intended Accelerator Framework) targets to
11 Because of the unified address, hardware and user space of process can
21 | User application (CPU) | | Hardware Accelerator |
45 The user drivers and libraries are called WarpDrive.
57 | | user API | |
58 | WarpDrive library | ------------> | user driver |
93 created when user application open the chrdev. The file descriptor is used
94 as the user handle of the queue.
96 a chrdev to the user space. The user application communicates with the
109 * @UACCE_QFRT_DUS: device user share region
[all …]
|
| /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/tools/rtla/ |
| D | common_timerlat_options.rst | 38 **-u**, **--user-threads**
40 Set timerlat to run without a workload, and then dispatches user-space workloads
42 adding so the measurement for the kernel-to-user and user-to-kernel to the tracer
43 output. **--user-threads** will be used unless the user specify **-k**.
45 **-U**, **--user-load**
47 Set timerlat to run without workload, waiting for the user to dispatch a per-cpu
49 See linux/tools/rtla/sample/timerlat_load.py for an example of user-load code.
|
| /Documentation/ABI/removed/ |
| 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
|
| /Documentation/networking/dsa/ |
| D | configuration.rst | 35 All other corresponding linux interfaces are called user interfaces.
37 The user interfaces depend on the conduit interface being up in order for them
39 interface had to be managed explicitly by the user. Starting with kernel v5.12,
42 - when a DSA user interface is brought up, the conduit interface is
44 - when the conduit interface is brought down, all DSA user interfaces are
56 a user interface
59 another user interface
62 a third user interface
65 A user interface dedicated for upstream traffic
100 # brought up manually before the user ports.
[all …]
|
| /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/translations/zh_CN/dev-tools/ |
| D | gdb-kernel-debugging.rst | 72 scanning for modules in /home/user/linux/build
73 loading @0xffffffffa0020000: /home/user/linux/build/net/netfilter/xt_tcpudp.ko
74 loading @0xffffffffa0016000: /home/user/linux/build/net/netfilter/xt_pkttype.ko
75 loading @0xffffffffa0002000: /home/user/linux/build/net/netfilter/xt_limit.ko
76 loading @0xffffffffa00ca000: /home/user/linux/build/net/packet/af_packet.ko
77 loading @0xffffffffa003c000: /home/user/linux/build/fs/fuse/fuse.ko
79 loading @0xffffffffa0000000: /home/user/linux/build/drivers/ata/ata_generic.ko
94 loading @0xffffffffa0034000: /home/user/linux/build/lib/libcrc32c.ko
95 loading @0xffffffffa0050000: /home/user/linux/build/lib/lzo/lzo_compress.ko
96 loading @0xffffffffa006e000: /home/user/linux/build/lib/zlib_deflate/zlib_deflate.ko
[all …]
|
| /Documentation/translations/zh_TW/dev-tools/ |
| D | gdb-kernel-debugging.rst | 68 scanning for modules in /home/user/linux/build
69 loading @0xffffffffa0020000: /home/user/linux/build/net/netfilter/xt_tcpudp.ko
70 loading @0xffffffffa0016000: /home/user/linux/build/net/netfilter/xt_pkttype.ko
71 loading @0xffffffffa0002000: /home/user/linux/build/net/netfilter/xt_limit.ko
72 loading @0xffffffffa00ca000: /home/user/linux/build/net/packet/af_packet.ko
73 loading @0xffffffffa003c000: /home/user/linux/build/fs/fuse/fuse.ko
75 loading @0xffffffffa0000000: /home/user/linux/build/drivers/ata/ata_generic.ko
90 loading @0xffffffffa0034000: /home/user/linux/build/lib/libcrc32c.ko
91 loading @0xffffffffa0050000: /home/user/linux/build/lib/lzo/lzo_compress.ko
92 loading @0xffffffffa006e000: /home/user/linux/build/lib/zlib_deflate/zlib_deflate.ko
[all …]
|
| /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.rst | 11 and the second one hardlimit. A user can never exceed a hardlimit for any
12 resource (unless he has CAP_SYS_RESOURCE capability). User is allowed to exceed
14 period" or "grace time". When grace time is over, user is not able to allocate
25 When user exceeds a softlimit, runs out of grace time or reaches hardlimit,
28 when user is using a graphical desktop he usually cannot see the message.
48 - UID/GID (depends on quota type) of user / group whose limit
51 - UID of a user who caused the event
70 - four warnings are also defined for the event when user stops
|
| D | affs.rst | 38 The muFS (multi user File System) equivalents of the above file systems
49 system to uid or the uid of the current user, respectively.
111 - R maps to r for user, group and others. On directories, R implies x.
123 User id and group id will be used unless set[gu]id are given as mount
124 options. Since most of the Amiga file systems are single user systems
126 Amiga filesystem will be owned by the user who actually mounts the
133 - r permission will allow R for user, group and others.
135 - w permission will allow W for user, group and others.
137 - x permission of the user will allow E for plain files.
139 - D will be allowed for user, group and others.
[all …]
|
| /Documentation/ABI/testing/ |
| D | debugfs-driver-habanalabs | 42 Description: Allows the root user to read or write directly through the
46 the generic Linux user-space PCI mapping) because the DDR bar
50 If the IOMMU is disabled, it also allows the root user to read
57 Description: Allows the root user to read or write 64 bit data directly
61 the generic Linux user-space PCI mapping) because the DDR bar
65 If the IOMMU is disabled, it also allows the root user to read
72 Description: Allows the root user to read from the device's internal
77 Linux user-space PCI mapping) because the amount of internal
82 in case it is done while the device is executing user
90 Description: Enables the root user to set the device to specific state.
[all …]
|
| D | sysfs-class-tee | 7 user-space daemon tee-supplicant or the RPMB subsystem
8 in the kernel. The value "user" means that the driver
9 will route the RPMB frames via user space. Conversely,
12 should be assumed that RPMB frames are routed via user
|
| /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/mm/damon/ |
| D | design.rst | 19 To know how user-space can do the configurations and start/stop DAMON, refer to
35 purposes that provides interfaces for the user space, on top of the core
77 To know how user-space can do the configuration via :ref:`DAMON sysfs interface
154 To know how user-space can set the attributes via :ref:`DAMON sysfs interface
225 three regions if the total number of regions will not exceed the user-specified
258 abstracted monitoring target memory area only for each of a user-specified time
261 User-space can get the monitoring results via DAMON sysfs interface and/or
295 including monitoring results and operation advice between kernel and user
302 the access pattern of interest, and applies the user-desired operation actions
303 to the regions, for every user-specified time interval called
[all …]
|
| /Documentation/trace/ |
| D | user_events.rst | 2 user_events: User-based Event Tracing
9 User based trace events allow user processes to create events and trace data
18 delete user based events via the u: prefix. The format of the command to
37 Registering within a user process is done via ioctl() out to the
83 must be naturally aligned and write accessible within the user program.
119 User based events show up under tracefs like any other event under the
148 User programs are encouraged to use clearly sized types like u32.
150 **NOTE:** *Long is not supported since size can vary between user and kernel.*
153 This allows user programs to describe custom structs out to tools, if required.
167 Deleting an event from within a user process is done via ioctl() out to the
[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 privilege.
94 in the kernel user keyring.
102 in the kernel user keyring.
[all …]
|
| /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/ABI/stable/ |
| D | sysfs-driver-firmware-zynqmp | 100 bit on FPD WDT expiration. If healthy bit is set by a user
122 This sysfs interface allows user to configure features at
123 runtime. The user can enable or disable features running at
124 firmware as well as the user can configure the parameters of
133 1. PM_FEATURE_OVERTEMP_STATUS = 1, the user can enable or
135 2. PM_FEATURE_OVERTEMP_VALUE = 2, the user can configure the
137 3. PM_FEATURE_EXTWDT_STATUS = 3, the user can enable or disable
139 4. PM_FEATURE_EXTWDT_VALUE = 4, the user can configure the
180 The user can enable or disable features running at firmware.
181 Also, the user can configure the parameters of the features
[all …]
|
12345678910>>...54