| /linux-5.10/tools/perf/util/ |
| D | strfilter.h | 23 * @rules: Filter rule, which is a combination of glob expressions.
24 * @err: Pointer which points an error detected on @rules
26 * Parse @rules and return new strfilter. Return NULL if an error detected.
30 struct strfilter *strfilter__new(const char *rules, const char **err);
35 * @rules: Filter rule to be appended at left of the root of
37 * @err: Pointer which points an error detected on @rules
39 * Parse @rules and join it to the @filter by using logical-or.
43 const char *rules, const char **err);
48 * @rules: Filter rule to be appended at left of the root of
50 * @err: Pointer which points an error detected on @rules
[all …]
|
| D | strfilter.c | 160 struct strfilter *strfilter__new(const char *rules, const char **err) in strfilter__new() argument
166 filter->root = strfilter_node__new(rules, &ep); in strfilter__new()
179 const char *rules, const char **err) in strfilter__append() argument
184 if (!filter || !rules) in strfilter__append()
187 right = strfilter_node__new(rules, &ep); in strfilter__append()
207 int strfilter__or(struct strfilter *filter, const char *rules, const char **err) in strfilter__or() argument
209 return strfilter__append(filter, true, rules, err); in strfilter__or()
212 int strfilter__and(struct strfilter *filter, const char *rules, in strfilter__and() argument
215 return strfilter__append(filter, false, rules, err); in strfilter__and()
238 /* Return true if STR matches the filter rules */
|
| /linux-5.10/Documentation/admin-guide/aoe/ |
| D | udev.txt | 1 # These rules tell udev what device nodes to create for aoe support.
11 # udev_rules="/etc/udev/rules.d/"
12 # bash# ls /etc/udev/rules.d/
13 # 10-wacom.rules 50-udev.rules
15 # /etc/udev/rules.d/60-aoe.rules
|
| D | udev-install.sh | 1 # install the aoe-specific udev rules from udev.txt into
22 # find the directory where udev rules are stored, often
23 # /etc/udev/rules.d
27 rules_d=/etc/udev/rules.d
30 echo "$me Error: cannot find udev rules directory" 1>&2
33 sh -xc "cp `dirname $0`/udev.txt $rules_d/60-aoe.rules"
|
| /linux-5.10/net/netfilter/ |
| D | nft_set_pipapo.c | 56 * represented as one or more rules, depending on the number of composing
61 * Rules are mapped between fields through an array of x, n pairs, with each
62 * item mapping a matched rule to one or more rules. The position of the pair in
65 * next-field rules the current rule maps to.
108 * or multiple rules for ranges. Ranges are expanded to composing netmasks
116 * - insert references to the rules in the lookup table, selecting buckets
144 * rules from the lookup table to rules belonging to the same entry in
147 * Note that as rules map to contiguous ranges of rules, given how netmask
182 * we need to map rules for 10.0.0.5 in lookup table #0 (rule #0) to 1024
183 * in lookup table #1 (rule #0) and rules for 192.168.1.0-192.168.2.1
[all …]
|
| D | nft_set_pipapo.h | 52 /* Each n-bit range maps to up to n * 2 rules */
92 * @n: Number of rules (in next field) this rule maps to
114 * @rules: Number of inserted rules
123 unsigned long rules; member
179 int pipapo_refill(unsigned long *map, int len, int rules, unsigned long *dst,
235 * of rules (composing netmasks) the entries expand to. We compute the worst
252 unsigned long rules; in pipapo_estimate_size() local
258 * field can expand to up to n * 2 rules in each bucket, and in pipapo_estimate_size()
261 rules = ilog2(desc->field_len[i] * BITS_PER_BYTE) * 2; in pipapo_estimate_size()
262 entry_size += rules * in pipapo_estimate_size()
[all …]
|
| D | nf_tables_core.c | 129 struct nft_rule *const *rules; member
162 struct nft_rule *const *rules; in nft_do_chain() local
176 rules = rcu_dereference(chain->rules_gen_1); in nft_do_chain()
178 rules = rcu_dereference(chain->rules_gen_0); in nft_do_chain()
181 rule = *rules; in nft_do_chain()
183 for (; *rules ; rules++) { in nft_do_chain()
184 rule = *rules; in nft_do_chain()
225 jumpstack[stackptr].rules = rules + 1; in nft_do_chain()
246 rules = jumpstack[stackptr].rules; in nft_do_chain()
|
| /linux-5.10/security/smack/ |
| D | Kconfig | 17 bool "Reporting on access granted by Smack rules"
21 Enable the bring-up ("b") access mode in Smack rules.
26 rules. The developer can use the information to
27 identify which rules are necessary and what accesses
54 delivering a signal in the Smack rules.
|
| /linux-5.10/Documentation/sound/designs/ |
| D | tracepoints.rst | 116 struct snd_pcm_hardware and rules of constraints in the runtime. The
117 structure describes capabilities of handled hardware. The rules describes
120 to compute the target parameter. ALSA PCM core registers some rules to the
129 2. In the same callback, drivers are also expected to register additional rules
156 device, rules of constraint and name of the changed parameter, in order. The
157 field for rules of constraint consists of two sub-fields; index of applied rule
158 and total number of rules added to the runtime. As an exception, the index 000
159 means that the parameter is changed by ALSA PCM core, regardless of the rules.
|
| /linux-5.10/Documentation/filesystems/ |
| D | directory-locking.rst | 16 1) read access. Locking rules: caller locks directory we are accessing.
19 2) object creation. Locking rules: same as above, but the lock is taken
22 3) object removal. Locking rules: caller locks parent, finds victim,
25 4) rename() that is _not_ cross-directory. Locking rules: caller locks
34 5) link creation. Locking rules:
44 rules:
61 The rules above obviously guarantee that all directories that are going to be
120 But locking rules for cross-directory rename guarantee that we do not
|
| /linux-5.10/Documentation/admin-guide/LSM/ |
| D | Smack.rst | 50 load the Smack access rules
154 This interface allows modification of existing access control rules.
217 This interface allows access control rules in addition to
218 the system defined rules to be specified. The format accepted
232 This interface allows access control rules in addition to
233 the system defined rules to be specified. The format accepted
248 This interface allows process specific access rules to be
249 defined. These rules are only consulted if access would
255 This interface allows process specific access rules to be
256 defined. These rules are only consulted if access would
[all …]
|
| /linux-5.10/kernel/ |
| D | audit_watch.c | 43 struct list_head rules; /* anchor for krule->rlist */ member
109 WARN_ON(!list_empty(&watch->rules)); in audit_put_watch()
168 INIT_LIST_HEAD(&watch->rules); in audit_init_watch()
200 /* Duplicate the given audit watch. The new watch's rules list is initialized
243 /* Update inode info in audit rules based on filesystem event. */
260 /* If the update involves invalidating rules, do the inode-based in audit_update_watch()
276 list_for_each_entry_safe(r, nextr, &owatch->rules, rlist) { in audit_update_watch()
297 list_add(&nentry->rule.rlist, &nwatch->rules); in audit_update_watch()
320 /* Remove all watches & rules associated with a parent that is going away. */
329 list_for_each_entry_safe(r, nextr, &w->rules, rlist) { in audit_remove_parent_watches()
[all …]
|
| /linux-5.10/net/sched/ |
| D | em_canid.c | 34 * Raw rules copied from netlink message; Used for sending
123 struct can_filter *conf = data; /* Array with rules */ in em_canid_change()
143 * We need two for() loops for copying rules into two contiguous in em_canid_change()
144 * areas in rules_raw to process all eff rules with a simple loop. in em_canid_change()
145 * NB: The configuration interface supports sff and eff rules. in em_canid_change()
152 /* Fill rules_raw with EFF rules first */ in em_canid_change()
163 /* append SFF frame rules */ in em_canid_change()
|
| /linux-5.10/tools/testing/selftests/ |
| D | Makefile | 91 # Clear LDFLAGS and MAKEFLAGS when implicit rules are missing. This provides
92 # implicit rules to sub-test Makefiles which avoids build failures in test
93 # Makefile that don't have explicit build rules.
139 # Invoke headers install with --no-builtin-rules to avoid circular
141 # make inherits builtin-rules which will use the rule generate
147 # invokes them as sub-makes and --no-builtin-rules is not necessary,
154 $(MAKE) --no-builtin-rules ARCH=$(ARCH) -C $(top_srcdir) headers_install
156 $(MAKE) --no-builtin-rules INSTALL_HDR_PATH=$$BUILD/usr \
|
| D | lib.mk | 13 # The following are built by lib.mk common compile rules.
32 # Invoke headers install with --no-builtin-rules to avoid circular
34 # make inherits builtin-rules which will use the rule generate
39 # invokes them as sub-makes and --no-builtin-rules is not necessary,
50 $(MAKE) --no-builtin-rules ARCH=$(ARCH) -C $(top_srcdir) headers_install
52 $(MAKE) --no-builtin-rules INSTALL_HDR_PATH=$$OUTPUT/usr \
|
| /linux-5.10/security/integrity/ima/ |
| D | Kconfig | 60 Disabling this option will disregard LSM based policy rules.
135 IMA policy can now be updated multiple times. The new rules get
136 appended to the original policy. Have in mind that the rules are
149 This option allows the root user to see the current policy rules.
176 bool "IMA build time configured policy rules"
183 policy rules persist after loading a custom policy.
185 Depending on the rules configured, this policy may require kernel
|
| D | ima_policy.c | 7 * - initialize default measure policy rules
207 /* An array of architecture specific rules */
359 * lsm rules can change in ima_lsm_copy_rule()
424 * The LSM policy can be reloaded, leaving the IMA LSM based rules referring
425 * to the old, stale LSM policy. Update the IMA LSM based rules to reflect
580 * we need to differentiate between calling hooks, for hook specific rules.
742 const char * const *rules; in ima_init_arch_policy() local
750 /* Get number of rules */ in ima_init_arch_policy()
751 for (rules = arch_rules; *rules != NULL; rules++) in ima_init_arch_policy()
759 /* Convert each policy string rules to struct ima_rule_entry format */ in ima_init_arch_policy()
[all …]
|
| /linux-5.10/tools/testing/selftests/drivers/net/mlxsw/ |
| D | tc_flower_scale.sh | 4 # Test for resource limit of offloaded flower rules. The test adds a given
6 # indication for all of the tc flower rules. This file contains functions to set
8 # script that calls the testing routine with a given number of rules.
116 check_err 1 "Invalid count of $count. At most 65536 rules supported"
|
| /linux-5.10/drivers/gpu/drm/etnaviv/ |
| D | state_blt.xml.h | 6 This file was generated by the rules-ng-ng headergen tool in this git repository:
7 http://0x04.net/cgit/index.cgi/rules-ng-ng
8 git clone git://0x04.net/rules-ng-ng
10 The rules-ng-ng source files this header was generated from are:
|
| /linux-5.10/Documentation/networking/ |
| D | tc-actions-env-rules.rst | 4 TC Actions - Environmental Rules
8 The "environmental" rules for authors of any new tc actions are:
23 The "environmental" rules for callers of actions (qdiscs etc) are:
|
| D | vrf.rst | 10 The VRF device combined with ip rules provides the ability to create virtual
21 the use of higher priority ip rules (Policy Based Routing, PBR) to take
22 precedence over the VRF device rules directing specific traffic as desired.
48 flow through the VRF device. Similarly on egress routing rules are used to
51 and out of the VRF as a whole\ [1]_. Similarly, netfilter\ [2]_ and tc rules
52 can be applied using the VRF device to specify rules that apply to the VRF
60 ingress device and both INPUT and PREROUTING rules with skb->dev set to
61 the VRF device. For egress POSTROUTING and OUTPUT rules can be written
76 with a different priority or install per-VRF rules.
78 Prior to the v4.8 kernel iif and oif rules are needed for each VRF device::
[all …]
|
| /linux-5.10/net/ceph/crush/ |
| D | crush.c | 121 /* rules */ in crush_destroy()
122 if (map->rules) { in crush_destroy()
125 crush_destroy_rule(map->rules[b]); in crush_destroy()
126 kfree(map->rules); in crush_destroy()
|
| /linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-block-dm | 7 Users: util-linux, device-mapper udev rules
16 Users: util-linux, device-mapper udev rules
25 Users: util-linux, device-mapper udev rules
|
| /linux-5.10/arch/powerpc/kernel/ |
| D | ima_arch.c | 17 * These rules verify the file signatures against known good values.
35 * These rules add the kexec kernel image and kernel modules file hashes to
45 * The "secure_and_trusted_rules" contains rules for both the secure boot and
|
| /linux-5.10/Documentation/arm/ |
| D | kernel_mode_neon.rst | 55 following rules and restrictions apply in the kernel:
89 kernel is by adhering to the following rules:
104 NEON assembler is supported with no additional caveats as long as the rules
112 supported as long as the rules above are followed.
119 observe the following in addition to the rules above:
|