/Linux-v5.4/fs/nfs/ |
D | nfs4namespace.c | 102 const struct nfs4_fs_locations *locations, in nfs4_validate_fspath() argument 111 fs_path = nfs4_pathname_string(&locations->fs_path, page2, PAGE_SIZE); in nfs4_validate_fspath() 297 const struct nfs4_fs_locations *locations) in nfs_follow_referral() argument 308 if (locations == NULL || locations->nlocations <= 0) in nfs_follow_referral() 322 error = nfs4_validate_fspath(dentry, locations, page, page2); in nfs_follow_referral() 328 for (loc = 0; loc < locations->nlocations; loc++) { in nfs_follow_referral() 329 const struct nfs4_fs_location *location = &locations->locations[loc]; in nfs_follow_referral() 483 const struct nfs4_fs_locations *locations) in nfs4_replace_transport() argument 489 if (locations == NULL || locations->nlocations <= 0) in nfs4_replace_transport() 500 for (loc = 0; loc < locations->nlocations; loc++) { in nfs4_replace_transport() [all …]
|
D | nfs4state.c | 2048 struct nfs4_fs_locations *locations = NULL; in nfs4_try_migration() local 2060 locations = kmalloc(sizeof(struct nfs4_fs_locations), GFP_KERNEL); in nfs4_try_migration() 2061 if (page == NULL || locations == NULL) { in nfs4_try_migration() 2067 result = nfs4_proc_get_locations(inode, locations, page, cred); in nfs4_try_migration() 2075 if (!(locations->fattr.valid & NFS_ATTR_FATTR_V4_LOCATIONS)) { in nfs4_try_migration() 2087 status = nfs4_replace_transport(server, locations); in nfs4_try_migration() 2100 kfree(locations); in nfs4_try_migration()
|
/Linux-v5.4/fs/nfsd/ |
D | export.c | 308 struct nfsd4_fs_location *locations = fsloc->locations; in nfsd4_fslocs_free() local 311 if (!locations) in nfsd4_fslocs_free() 315 kfree(locations[i].path); in nfsd4_fslocs_free() 316 kfree(locations[i].hosts); in nfsd4_fslocs_free() 319 kfree(locations); in nfsd4_fslocs_free() 320 fsloc->locations = NULL; in nfsd4_fslocs_free() 408 if (fsloc->locations) in fsloc_parse() 420 fsloc->locations = kcalloc(fsloc->locations_count, in fsloc_parse() 423 if (!fsloc->locations) in fsloc_parse() 432 fsloc->locations[i].hosts = kstrdup(buf, GFP_KERNEL); in fsloc_parse() [all …]
|
D | export.h | 29 struct nfsd4_fs_location *locations; member
|
/Linux-v5.4/Documentation/hwmon/ |
D | nct6683.rst | 36 Limit register locations on Intel boards with EC firmware version 1.0 37 build date 04/03/13 do not match the register locations in the Nuvoton 43 Some of the register locations can be reverse engineered; others are too
|
/Linux-v5.4/arch/arm/nwfpe/ |
D | softfloat-macros | 138 which are stored at the locations pointed to by `z0Ptr' and `z1Ptr'. 174 the locations pointed to by `z0Ptr' and `z1Ptr'. 214 stored at the locations pointed to by `z0Ptr' and `z1Ptr'. The bits shifted 223 and the integer part of the result is returned at the locations pointed to 285 pieces which are stored at the locations pointed to by `z0Ptr' and `z1Ptr'. 304 64-bit pieces which are stored at the locations pointed to by `z0Ptr', 341 are stored at the locations pointed to by `z0Ptr' and `z1Ptr'. 361 64-bit pieces which are stored at the locations pointed to by `z0Ptr', 400 64-bit pieces which are stored at the locations pointed to by `z0Ptr' and 419 result is broken into three 64-bit pieces which are stored at the locations [all …]
|
/Linux-v5.4/Documentation/filesystems/ext4/ |
D | globals.rst | 7 have static metadata at fixed locations.
|
D | bitmaps.rst | 20 ext2fs\_test\_block\_bitmap2() will return '0' for those locations,
|
D | about.rst | 30 Throughout this document, disk locations are given in terms of these
|
/Linux-v5.4/tools/memory-model/litmus-tests/ |
D | SB+rfionceonce-poonceonces.litmus | 31 locations [0:r1; 1:r3; x; y] (* Debug aid: Print things not in "exists". *)
|
D | README | 119 also demonstrates the "locations" debugging aid, which designates 120 additional registers and locations to be printed out in the dump 121 of final states in the herd7 output. Without the "locations" 122 statement, only those registers and locations mentioned in the
|
/Linux-v5.4/Documentation/devicetree/bindings/dma/ |
D | ste-coh901318.txt | 8 - reg: register locations and length
|
/Linux-v5.4/Documentation/devicetree/bindings/spi/ |
D | atmel-quadspi.txt | 7 - reg: Should contain the locations and lengths of the base registers
|
/Linux-v5.4/Documentation/devicetree/bindings/display/etnaviv/ |
D | etnaviv-drm.txt | 7 identification registers at fixed locations, which provide all the
|
/Linux-v5.4/arch/arc/lib/ |
D | strcmp-archs.S | 27 ;; Check if the read locations are the same
|
/Linux-v5.4/Documentation/devicetree/bindings/mtd/partitions/ |
D | brcm,trx.txt | 9 identification fields, CRC32 checksum and the locations of embedded partitions.
|
/Linux-v5.4/arch/arm/boot/dts/ |
D | integrator.dtsi | 78 * These PrimeCells are in the same locations and using the
|
/Linux-v5.4/sound/pci/ac97/ |
D | ac97_proc.c | 31 static const char *locations[8] = { in snd_ac97_proc_read_functions() local 52 locations[sense_info >> 13]); in snd_ac97_proc_read_functions()
|
/Linux-v5.4/Documentation/admin-guide/device-mapper/ |
D | dm-dust.txt | 5 locations, and the ability to enable the emulation of the failures 28 messages to add arbitrary bad blocks at new locations, and the 257 dm-flakey fails all I/O from all block locations at a specified time
|
/Linux-v5.4/Documentation/devicetree/bindings/mfd/ |
D | qcom,spmi-pmic.txt | 7 locations/definitions within these regions, with some of these regions
|
/Linux-v5.4/Documentation/arm64/ |
D | tagged-pointers.rst | 38 Using non-zero address tags in any of these locations when the
|
/Linux-v5.4/Documentation/s390/ |
D | zfcpdump.rst | 33 under the following locations:
|
/Linux-v5.4/Documentation/devicetree/bindings/serial/ |
D | qcom,msm-uartdm.txt | 16 - reg: Should contain UART register locations and lengths. The first
|
/Linux-v5.4/Documentation/security/ |
D | lsm.rst | 186 capabilities module. There are still a few locations in the base kernel 190 locations would need to be changed if the capability-related fields were 192 locations that still perform such direct examination or modification of
|
/Linux-v5.4/Documentation/driver-api/ |
D | vme.rst | 252 monitoring adjacent locations. The function :c:func:`vme_lm_count` can be used 253 to determine how many locations are provided. 270 location. Each location monitor can monitor a number of adjacent locations. The
|