| /Linux-v6.1/fs/nls/ |
| D | Kconfig | 27 system (if different) to store data (filenames) on a disk.
43 The Microsoft FAT file system family can deal with filenames in
46 codepage if you want to be able to read/write these filenames on
47 DOS/Windows partitions correctly. This does apply to the filenames
55 The Microsoft FAT file system family can deal with filenames in
58 codepage if you want to be able to read/write these filenames on
59 DOS/Windows partitions correctly. This does apply to the filenames
67 The Microsoft FAT file system family can deal with filenames in
70 codepage if you want to be able to read/write these filenames on
71 DOS/Windows partitions correctly. This does apply to the filenames
[all …]
|
| /Linux-v6.1/tools/testing/selftests/bpf/ |
| D | veristat.c | 63 char **filenames; member
185 tmp = realloc(env.filenames, (env.filename_cnt + 1) * sizeof(*env.filenames)); in parse_arg()
188 env.filenames = tmp; in parse_arg()
189 env.filenames[env.filename_cnt] = strdup(arg); in parse_arg()
190 if (!env.filenames[env.filename_cnt]) in parse_arg()
830 err = process_obj(env.filenames[i]); in handle_verif_mode()
832 fprintf(stderr, "Failed to process '%s': %d\n", env.filenames[i], err); in handle_verif_mode()
1185 err = parse_stats_csv(env.filenames[0], &base_specs, in handle_comparison_mode()
1188 fprintf(stderr, "Failed to parse stats from '%s': %d\n", env.filenames[0], err); in handle_comparison_mode()
1191 err = parse_stats_csv(env.filenames[1], &comp_specs, in handle_comparison_mode()
[all …]
|
| /Linux-v6.1/Documentation/filesystems/ |
| D | isofs.rst | 20 ASCII. Joliet filenames are stored in Unicode format, but
33 check=relaxed Matches filenames with different cases
34 check=strict Matches only filenames with the exact same case
36 map=off Do not map non-Rock Ridge filenames to lower case
37 map=normal Map non-Rock Ridge filenames to lower case
|
| D | fscrypt.rst | 30 However, except for filenames, fscrypt does not encrypt filesystem
39 needed. eCryptfs also limits encrypted filenames to 143 bytes,
57 protects the confidentiality of file contents and filenames in the
90 plaintext file contents or filenames from other users on the same
137 - In general, decrypted contents and filenames in the kernel VFS
179 greater of the security strength of the contents and filenames
263 suitable for both contents and filenames encryption, and it accepts
272 (contents or filenames) is encrypted, the file's 16-byte nonce is
290 key and a single filenames encryption key. To still encrypt different
323 plaintext filenames, the KDF is also used to derive a 128-bit
[all …]
|
| D | qnx6.rst | 88 its longname. (filenames longer than 27 characters)
116 One special case are long filenames or subdirectory names.
140 Long filenames
143 Long filenames are stored in a separate addressing tree. The staring point
|
| D | hfsplus.rst | 9 blocks, 255-character unicode filenames, and file sizes of 2^63 bytes.
|
| D | vfat.rst | 64 Unicode characters. Long filenames are stored on disk
85 restore filenames that are created with any Unicode
300 Windows 95 but it is used by Windows NT. The case of filenames is not
|
| D | ext2.rst | 191 the filenames in the directory; a pending enhancement uses hashing of the
192 filenames to allow lookup without the need to scan the entire directory.
348 have to be 8 character filenames, even then we are fairly close to
349 running out of unique filenames.
|
| D | hpfs.rst | 63 As in OS/2, filenames are case insensitive. However, shell thinks that names
232 0.93 Fixed bug that locked up the machine when there were too many filenames
241 using 0xff in filenames.
|
| D | ramfs-rootfs-initramfs.rst | 186 cpio -i -d -H newc -F initramfs_data.cpio --no-absolute-filenames
215 of filenames is with the find command; you should give find the -depth
|
| D | affs.rst | 212 By default, filenames are truncated to 30 characters without warning.
|
| /Linux-v6.1/tools/testing/selftests/powerpc/ptrace/ |
| D | core-pkey.c | 258 char *filenames, *filename[3]; in parent() local
291 filename[0] = filenames = malloc(PATH_MAX); in parent()
292 if (!filenames) { in parent()
344 free(filenames); in parent()
|
| /Linux-v6.1/fs/isofs/ |
| D | Kconfig | 8 long Unix filenames and symbolic links are also supported by this
24 which allows for long filenames in unicode format (unicode is the
|
| /Linux-v6.1/scripts/clang-tools/ |
| D | gen_compile_commands.py | 88 for dirpath, dirnames, filenames in os.walk(directory, topdown=True):
94 for filename in filenames:
|
| /Linux-v6.1/fs/exfat/ |
| D | Kconfig | 20 filenames and the UTF-16 character encoding that the exFAT
|
| /Linux-v6.1/tools/testing/selftests/tc-testing/ |
| D | tdc.py | 48 for dirpath, dirnames, filenames in os.walk(plugindir):
49 for fn in filenames:
649 for root, dirnames, filenames in os.walk(testdir):
650 for filename in fnmatch.filter(filenames, '*.json'):
|
| /Linux-v6.1/scripts/dtc/ |
| D | dtc-lexer.l | 80 /* Don't allow nuls in filenames */
|
| /Linux-v6.1/Documentation/kbuild/ |
| D | reproducible-builds.rst | 49 Absolute filenames
53 absolute filenames for the source files. This must be overridden by
|
| /Linux-v6.1/fs/fat/ |
| D | Kconfig | 53 support" below), or you will not be able to see the long filenames
66 long filenames. That includes non-compressed FAT-based file systems
|
| /Linux-v6.1/fs/reiserfs/ |
| D | Kconfig | 10 Reiserfs stores not just filenames but the files themselves in a
|
| /Linux-v6.1/tools/perf/ |
| D | builtin-record.c | 92 char **filenames; member
1832 if (rec->switch_output.filenames[n]) { in record__switch_output()
1833 remove(rec->switch_output.filenames[n]); in record__switch_output()
1834 zfree(&rec->switch_output.filenames[n]); in record__switch_output()
1836 rec->switch_output.filenames[n] = new_filename; in record__switch_output()
4076 rec->switch_output.filenames = calloc(sizeof(char *), in cmd_record()
4078 if (!rec->switch_output.filenames) { in cmd_record()
|
| /Linux-v6.1/Documentation/filesystems/caching/ |
| D | cachefiles.rst | 232 if they do. Their filenames all begin "D..." or "E...". If represented as a
236 Special objects are similar to data objects, except their filenames begin
269 object filenames indicate the encoding:
|
| /Linux-v6.1/Documentation/admin-guide/cifs/ |
| D | usage.rst | 259 Valid filenames differ between Windows and Linux. Windows typically restricts
260 filenames which contain certain reserved characters (e.g.the character :
262 Linux allows a slightly wider set of valid characters in filenames. Windows
265 filenames (ie those which contain valid Linux characters, which normally
565 characters forbidden in typical CIFS filenames, without
|
| /Linux-v6.1/Documentation/admin-guide/ |
| D | rtc.rst | 28 different filenames of course), but the hardware may not offer the
|
| /Linux-v6.1/fs/affs/ |
| D | Changes | 214 invalid filenames didn't work correctly.
|
