| /linux/Documentation/filesystems/ |
| H A D | ntfs3.rst | 14 compressed files.
25 Note: Applied to empty files, this allows to switch type between
56 - Controls the default permissions for files/directories created after
60 - :rspan:`1` Instead of specifying umask which applies both to files and
61 directories, fmask applies only to files and dmask only to directories.
65 - Files with the Windows-specific HIDDEN (FILE_ATTRIBUTE_HIDDEN) attribute
69 - Files with the Windows-specific SYSTEM (FILE_ATTRIBUTE_SYSTEM) attribute
70 will be marked as system immutable files.
74 when creating and moving or renaming files. Files whose names start
75 with a dot will have the HIDDEN attribute set and files whose names
[all …]
|
| H A D | files.rst | 7 This document describes how locking for files (struct file)
8 and file descriptor table (struct files) works.
11 with a lock (files->file_lock) and reference count (files->count).
18 The files (struct file) themselves are protected using
33 and files->fdtab points to the new structure. The fdtable
46 fdt = files_fdtable(files);
61 3. For any update to the fd table, files->file_lock must
89 holding files->file_lock. If ->file_lock is dropped, then
90 another thread expand the files thereby creating a new
95 spin_lock(&files->file_lock);
[all …]
|
| H A D | zonefs.rst | 13 constraint of zoned block devices to the user. Files representing sequential
60 Zonefs exposes the zones of a zoned block device as files. The files
85 Files representing zones of the same type are grouped together under the same
101 obtained with the stat() or fstat() system calls, indicates the number of files
104 Zone files
107 Zone files are named using the number of the zone they represent within the set
109 contain files named "0", "1", "2", ... The file numbers also represent
112 All read and write operations to zone files are not allowed beyond the file
116 Creating, deleting, renaming or modifying any attribute of files and
122 Conventional zone files
[all …]
|
| H A D | fsverity.rst | 14 of read-only files. Currently, it is supported by the ext4, f2fs, and
20 but works on files rather than block devices. On regular files on
52 (APK) files, for example. These typically contain many translations,
62 still be used on read-only filesystems. fs-verity is for files that
72 files can be trusted to authenticate them. Consider e.g. an
73 application that wants to authenticate data files before using them,
85 "IMA appraisal" enforces that files contain a valid, matching
90 control decisions based on immutable security properties of files,
93 files using properties ``fsverity_digest`` for identifying
94 files by their verity digest, and ``fsverity_signature`` to authorize
[all …]
|
| H A D | hfs.rst | 26 used for creating new files. Default values: '????'.
29 Specifies the user/group that owns all files on the filesystems.
33 Specifies the umask used for all files , all directories or all
34 files and directories. Defaults to the umask of the mounting process.
58 and gid of files.
59 * You can't create hard- or symlinks, device files, sockets or FIFOs.
62 non-standard forks are represented as hidden additional files in the normal
66 * You can't create, delete or rename resource forks of files or the
70 * Copying files to a different filesystem will loose those attributes
|
| /linux/drivers/comedi/drivers/ni_routing/tools/ |
| H A D | Makefile | 2 # this make file is simply to help autogenerate these files:
12 @echo "\`make csv-files\`"
13 @echo " Creates new csv-files using content of c-files of existing"
14 @echo " ni_routing/* content. New csv files are placed in csv"
16 @echo "\`make c-files\`"
17 @echo " Creates new c-files using content of csv sub-directory. These"
18 @echo " new c-files can be compared to the active content in the"
25 @echo " Remove all generated files/directories EXCEPT for csv/c files."
27 @echo " Remove all generated files/directories."
29 @echo " Build all csv-files, then all new c-files."
[all …]
|
| /linux/Documentation/dev-tools/ |
| H A D | gcov.rst | 13 This will create source code files annotated with execution counts
54 To enable profiling for specific files or directories, add a line
61 - For all files in one directory::
65 To exclude files from being profiled even when CONFIG_GCOV_PROFILE_ALL
74 Only files which are linked to the main kernel image or are compiled as
89 Files chapter
92 The gcov kernel support creates the following files in debugfs:
95 Parent directory for all gcov-related files.
143 gcc version used for kernel build. Also the following files need to be
147 - all C source files + headers
[all …]
|
| /linux/tools/testing/selftests/rcutorture/bin/ |
| H A D | kvm-find-errors.sh | 4 # Invoke a text editor on all console.log files for all runs with diagnostics,
5 # that is, on all such files having a console.log.diags counterpart.
30 files=
38 files="$files $i.diags $i"
42 files="$files $i.diags $i"
45 if test -n "$files"
47 $editor $files
59 files=
64 files="$files $i.diags $i"
67 if test -n "$files"
[all …]
|
| /linux/Documentation/ABI/stable/ |
| H A D | sysfs-driver-mlxreg-io | 8 The files are read only.
15 Description: These files show with which CPLD versions have been burned
18 The files are read only.
28 The files are read only.
34 Description: These files show with which CPLD versions have been burned
37 The files are read only.
43 Description: These files enable and disable the access to the JTAG domain.
66 Description: These files allow asserting system power cycling, switching
79 The files are write only.
93 Description: These files show the system reset cause, as following: power
[all …]
|
| /linux/ |
| H A D | .gitignore | 3 # NOTE! Don't add files that are generated in specific
7 # NOTE! Please use 'git ls-files -i -c --exclude-per-directory=.gitignore'
9 # any tracked files which get ignored after the change.
59 # Top-level generic files
97 # pacman files (make pacman-pkg)
103 # We don't want to ignore the following even if they are dot-files
116 # Generated include files
125 # quilt's files
129 # ctags files
133 # cscope files
[all …]
|
| /linux/scripts/ |
| H A D | make_fit.py | 8 """Build a FIT containing a lot of devicetree files
15 Creates a FIT containing the supplied kernel and a set of devicetree files,
28 looks at the .cmd files produced by the kernel build.
66 epilog = 'Build a FIT from a directory tree containing .dtb files'
87 help='Specifies the devicetree files to process')
150 for model, compat, files in entries:
155 fsw.property('fdt', bytes(''.join(f'fdt-{x}\x00' for x in files), "ascii"))
225 files: list of filenames corresponding to the DTB
243 files = cmd.split()
244 files = files[files.index('-i') + 1:]
[all …]
|
| H A D | checktransupdate.py | 13 This will print all the files that need to be updated or translated in the zh_CN locale.
142 """List all files with the specified suffix in the folder and its subfolders"""
143 files = []
151 # list all files and folders
158 files.append(ab_item)
160 return files
207 help="Locale to check when files are not specified",
214 help="Print files that do not have translations",
229 "files", nargs="*", help="Files to check, if not specified, check all files"
237 # Get files related to linux path
[all …]
|
| H A D | checkkconfigsymbols.py | 70 help="ignore files matching this Python regex "
165 files = sorted(undefined_b.get(symbol))
166 undefined[symbol] = files
167 # check if there are new files that reference the undefined symbol
169 files = sorted(undefined_b.get(symbol) -
171 if files:
172 undefined[symbol] = files
185 files = sorted(undefined.get(symbol))
186 print("%s: %s" % (yel("Referencing files"), ", ".join(files)))
293 """Return a list of all files in the current git directory."""
[all …]
|
| /linux/Documentation/admin-guide/mm/damon/ |
| H A D | usage.rst | 19 features by reading from and writing to special sysfs files. Therefore,
21 reads/writes the sysfs files instead of you. The `DAMON user space tool
42 creates multiple directories and files under its sysfs directory,
44 from the files under the directory.
56 Files Hierarchy
59 The files hierarchy of DAMON sysfs interface is shown below. In the below
61 directory is having ``/`` suffix, and files in each directory are separated by
107 has one directory named ``admin``. The directory contains the files for
116 Under the ``admin`` directory, one directory, ``kdamonds``, which has files for
129 In each kdamond directory, two files (``state`` and ``pid``) and one directory
[all …]
|
| /linux/Documentation/filesystems/spufs/ |
| H A D | spufs.rst | 25 set of files. These files can be used for manipulating the state of the
26 logical SPU. Users can change permissions on those files, but not actu-
27 ally add or remove files.
40 Files chapter
43 The files in spufs mostly follow the standard behavior for regular sys-
49 All files that support the read(2) operation also support readv(2) and
50 all files that support the write(2) operation also support writev(2).
51 All files support the access(2) and stat(2) family of operations, but
55 All files support the chmod(2)/fchmod(2) and chown(2)/fchown(2) opera-
59 The current set of files is:
[all …]
|
| /linux/drivers/gpu/drm/i915/gt/ |
| H A D | intel_gt_debugfs.c | 75 static const struct intel_gt_debugfs_file files[] = { in gt_debugfs_register() local
80 intel_gt_debugfs_register_files(root, files, ARRAY_SIZE(files), gt); in gt_debugfs_register()
106 const struct intel_gt_debugfs_file *files, in intel_gt_debugfs_register_files() argument
110 umode_t mode = files->fops->write ? 0644 : 0444; in intel_gt_debugfs_register_files()
112 if (!files->eval || files->eval(data)) in intel_gt_debugfs_register_files()
113 debugfs_create_file(files->name, in intel_gt_debugfs_register_files()
115 files->fops); in intel_gt_debugfs_register_files()
117 files++; in intel_gt_debugfs_register_files()
|
| /linux/tools/testing/selftests/pstore/ |
| H A D | pstore_post_reboot_tests | 40 prlog -n "Checking dmesg files exist in pstore filesystem ... "
43 prlog -n "Checking console files exist in pstore filesystem ... "
46 prlog -n "Checking pmsg files exist in pstore filesystem ... "
49 prlog -n "Checking dmesg files contain oops end marker"
53 files=`ls dmesg-${backend}-*`
54 operate_files $? "$files" grep_end_trace
76 prlog -n "Removing all files in pstore filesystem "
77 files=`ls *-${backend}-*`
78 operate_files $? "$files" rm
|
| /linux/Documentation/process/ |
| H A D | license-rules.rst | 18 as a whole, though individual source files can have a different license
28 Aside from that, individual files can be provided under a dual license,
32 The User-space API (UAPI) header files, which describe the interface of
37 into any source files which create an executable running on the Linux
53 The Linux kernel requires the precise SPDX identifier in all source files.
63 The SPDX license identifier in kernel files shall be added at the first
65 of files this is the first line, except for scripts which require the
86 files. There was build breakage observed with generated .lds files where
109 For example, the linux kernel UAPI files use the expression::
125 to be selected. For example, some dtsi files are available under dual
[all …]
|
| /linux/tools/perf/util/ |
| H A D | data.c | 23 static void close_dir(struct perf_data_file *files, int nr) in close_dir() argument
26 close(files[nr].fd); in close_dir()
27 zfree(&files[nr].path); in close_dir()
29 free(files); in close_dir()
34 close_dir(data->dir.files, data->dir.nr); in perf_data__close_dir()
40 struct perf_data_file *files = NULL; in perf_data__create_dir() local
46 files = zalloc(nr * sizeof(*files)); in perf_data__create_dir()
47 if (!files) in perf_data__create_dir()
51 struct perf_data_file *file = &files[i]; in perf_data__create_dir()
79 data->dir.files = files; in perf_data__create_dir()
[all …]
|
| /linux/scripts/clang-tools/ |
| H A D | gen_compile_commands.py | 25 # files in a different format. Do not support it.
36 paths: The list of files/directories to handle to find .cmd files.
38 usage = 'Creates a compile_commands.json database from kernel .cmd files'
59 paths_help = ('directories to search or files to parse '
60 '(files should be *.o, *.a, or modules.order). '
74 """Generate the iterator of .cmd files found under the directory.
79 directory: The directory to search for .cmd files.
113 """Generate the iterator of .cmd files associated with the archive.
128 """Generate the iterator of .cmd files associated with the modules.order.
156 root_directory: The directory that was searched for .cmd files. Usually
[all …]
|
| /linux/Documentation/kbuild/ |
| H A D | makefiles.rst | 22 (the resident kernel image) and modules (any module files).
46 any kernel Makefiles (or any other source files).
65 The kbuild files
72 The preferred name for the kbuild files are ``Makefile`` but ``Kbuild`` can
83 These lines define the files to be built, any special compilation
109 The kbuild Makefile specifies object files for vmlinux
113 Kbuild compiles all the $(obj-y) files. It then calls
114 ``$(AR) rcSTP`` to merge these files into one built-in.a file.
118 The order of files in $(obj-y) is significant. Duplicates in
132 # Each configuration option enables a list of files.
[all …]
|
| /linux/tools/usb/usbip/ |
| H A D | INSTALL | 21 It may also create one or more `.h' files containing system-dependent
31 cache files.
58 4. Type `make install' to install the programs and any data files and
61 5. You can remove the program binaries and object files from the
63 files that `configure' created (so you can compile the package for
67 all sorts of other programs in order to regenerate files that came
71 files again.
92 same time, by placing the object files for each architecture in their
94 directory where you want the object files and executables to go and run
107 `/usr/local/bin', include files under `/usr/local/include', etc. You
[all …]
|
| /linux/fs/jffs2/ |
| H A D | LICENCE | 1 The files in this directory and elsewhere which refer to this LICENCE
20 As a special exception, if other files instantiate templates or use
21 macros or inline functions from these files, or you compile these
22 files and link them with other works to produce a work based on these
23 files, these files do not by themselves cause the resulting work to be
25 these files must still be made available in accordance with section (3)
|
| /linux/tools/power/cpupower/bindings/python/ |
| H A D | README | 1 This folder contains the necessary files to build the Python bindings for
2 libcpupower (aside from the libcpupower object files).
8 * You need the object files in the libcpupower directory compiled by
19 files. For these bindings that means GPL v2.
30 Install SWIG and the Python development files provided by your distribution.
32 Build the object files for libcpupower by running make in the cpupower
43 Please verify the _raw_pylibcpupower.so and raw_pylibcpupower.py files have
|
| /linux/Documentation/devicetree/bindings/ |
| H A D | writing-schema.rst | 6 Devicetree bindings are written using json-schema vocabulary. Schema files are
24 references to other files specified in schema "$ref" properties. A $ref value
28 local files, but there may not actually be files present at those locations.
108 validation of DT files.
120 boilerplate. The tools process the schema files to produce the final schema for
146 binding documents and validate DTS files using the DT schema. The DT schema
151 Note that 'dtschema' installation requires 'swig' and Python development files
171 In order to perform validation of DT source files, use the ``dtbs_check`` target::
175 Note that ``dtbs_check`` will skip any binding schema files with errors. It is
177 binding schema files.
[all …]
|