/openbmc/qemu/tests/qemu-iotests/ |
H A D | 182 | 4 # Test image locking for POSIX locks 52 _launch_qemu -drive file=$TEST_IMG,if=none,id=drive0,file.locking=on \ 58 -drive file=$TEST_IMG,if=none,id=drive0,file.locking=on \ 90 'locking': 'on' 116 'locking': 'on' 151 _launch_qemu -drive file=$TEST_IMG,if=none,file.locking=on
|
H A D | 182.out | 6 QEMU_PROG: -drive file=TEST_DIR/t.qcow2,if=none,id=drive0,file.locking=on: Failed to get "write" lo… 18 'locking': 'on' 34 'locking': 'on'
|
H A D | 226 | 59 $QEMU_IO -c "open -r -o driver=$PROTO,filename=/dev/null,locking=off" 2>&1 | _filter_imgfmt 62 $QEMU_IO -c "open -o driver=$PROTO,filename=/dev/null,locking=off" 2>&1 | _filter_imgfmt
|
H A D | 245 | 162 self.reopen(opts, {'file.locking': 'off'}, "Cannot change the option 'locking'") 366 'locking': 'off', # This one can NOT be changed 378 # file.locking cannot be changed nor reset to the default value 379 self.reopen(opts, { 'file.locking': 'on' }, "Cannot change the option 'locking'") 380 del opts['file']['locking'] 381 self.reopen(opts, {}, "Option 'locking' cannot be reset to its default value") 383 self.reopen(opts, { 'file.locking': 'off' }) 756 opts['file']['locking'] = 'on' 759 # 'locking' cannot be changed 760 del opts['file']['locking'] [all …]
|
/openbmc/phosphor-host-ipmid/user_channel/ |
H A D | shadowlock.hpp | 20 * @brief Responsible for locking and unlocking /etc/shadow 35 lg2::error("Locking Shadow failed"); in Lock() 43 lg2::error("Un-Locking Shadow failed"); in ~Lock()
|
/openbmc/openbmc/poky/documentation/dev-manual/ |
H A D | bblock.rst | 3 Locking and Unlocking Recipes Using ``bblock`` 32 Locking tasks and recipes 43 Locking a recipe means locking all tasks of the recipe. If you need to 83 Locking mechanism
|
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Inventory/Item/PersistentMemory/ |
H A D | SecurityCapabilities.interface.yaml | 15 An indication of whether this memory supports the locking. 19 An indication of whether this memory supports data locking.
|
/openbmc/openbmc/meta-openembedded/meta-python/recipes-extended/python3-portalocker/ |
H A D | python3-portalocker_3.1.1.bb | 1 SUMMARY = "Cross-platform locking library" 2 DESCRIPTION = "Portalocker is a library to provide an easy API to file locking"
|
/openbmc/docs/designs/ |
H A D | estoraged.md | 71 different devices will have different command sets for device locking, e.g. 112 For eMMC devices, we plan to enable the password locking feature (CMD42), to 119 Support for hardware locking on other types of devices can be added as needed, 120 but at the very least, encryption-only locking will be available, even if 121 hardware locking isn't supported for a particular device. 125 and the device password (if hardware locking is available). The passwords will
|
/openbmc/u-boot/doc/ |
H A D | README.N1213 | 24 - TLB locking support 36 - Cache locking support.
|
/openbmc/u-boot/include/ |
H A D | armcoremodule.h | 23 #define CMVAL_LOCK1 0x0000A000 /* locking value */ 24 #define CMVAL_LOCK2 0x0000005F /* locking value */
|
/openbmc/qemu/tests/unit/ |
H A D | test-image-locking.c | 2 * Image locking tests 155 g_test_add_func("/image-locking/basic", test_image_locking_basic); in main() 156 g_test_add_func("/image-locking/set-perm-abort", test_set_perm_abort); in main()
|
/openbmc/qemu/docs/system/ |
H A D | qemu-block-drivers.rst.inc | 866 Disk image file locking 876 File Descriptor (OFD) locking API, and can be configured to fall back to POSIX 877 locking if the POSIX host doesn't support Linux OFD locking. 879 To explicitly enable image locking, specify "locking=on" in the file protocol 880 driver options. If OFD locking is not possible, a warning will be printed and 881 the POSIX locking API will be used. In this case there is a risk that the lock 883 shortcomings of the POSIX locking API. 899 Alternatively, locking can be fully disabled by "locking=off" block device 901 "file.locking=off" as the protocol driver is normally placed as a "file" child 906 -blockdev driver=qcow2,file.filename=/path/to/image,file.locking=off,file.driver=file [all …]
|
/openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/ |
H A D | python3-pid_3.0.4.bb | 1 SUMMARY = "Pidfile featuring stale detection and file-locking, can also \
|
H A D | python3-lockfile_0.12.2.bb | 4 SUMMARY = "Platform-independent file locking module"
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-benchmark/lmbench/lmbench/ |
H A D | 0001-doc-Fix-typos-in-manual-pages.patch | 37 lat_fcntl \- fcntl file locking benchmark 66 -lat_fcntl \- fcntl file locking benchmark
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/procmail/procmail/ |
H A D | from-debian-to-modify-parameters.patch | 105 -/*#define NO_flock_LOCK /* use of those kernel-locking methods */ 106 +#define NO_flock_LOCK /* use of those kernel-locking methods */ 109 if you want to disable particular locking styles but are unsure which
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-dbs/mysql/mariadb/ |
H A D | my.cnf | 16 skip-external-locking
|
/openbmc/openbmc/poky/meta/recipes-support/libdaemon/ |
H A D | libdaemon_0.14.bb | 4 as well as file locking to ensure that only a single copy of a given daemon \
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/lockdev/ |
H A D | lockdev_1.0.3.bb | 1 SUMMARY = "Locking devices library"
|
/openbmc/qemu/docs/devel/ |
H A D | multi-thread-tcg.rst | 86 per-vCPU basis won't need locking unless other vCPUs will need to 89 DESIGN REQUIREMENT: Add locking around all code generation and TB 100 requiring no locking during translation. 228 to do its own locking. 359 this may be a problem - typically presenting a locking ABI which
|
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/User/ |
H A D | AccountPolicy.interface.yaml | 8 Configures the maximum permissible attempt before locking out the
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/uw-imap/uw-imap/ |
H A D | imap-2007f-format-security.patch | 14 sprintf (tmp,"File locking failure: %s",strerror (errno));
|
/openbmc/phosphor-user-manager/ |
H A D | shadowlock.hpp | 24 * @brief Responsible for locking and unlocking /etc/shadow
|
/openbmc/qemu/replay/ |
H A D | replay-time.c | 24 * Due to the caller's locking requirements we get the icount from it in replay_save_clock()
|