| /Linux-v6.1/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-v6.1/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-v6.1/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 …]
|
| /Linux-v6.1/kernel/kcsan/ |
| D | permissive.h | 3 * Special rules for ignoring entire classes of data-racy memory accesses. None
4 * of the rules here imply that such data races are generally safe!
6 * All rules in this file can be configured via CONFIG_KCSAN_PERMISSIVE. Keep
20 * Access ignore rules based on address.
35 * Data race ignore rules based on access type and value change patterns.
44 * Rules here are only for plain read accesses, so that we still report in kcsan_ignore_data_race()
70 * The rules here will ignore the data races if we observe no more than in kcsan_ignore_data_race()
|
| /Linux-v6.1/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-v6.1/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-v6.1/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-v6.1/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-v6.1/Documentation/networking/ |
| D | representors.rst | 68 fast-path rules in the virtual switch. Packets transmitted on the
76 3. It acts as a handle by which switching rules (such as TC filters) can refer
77 to the representee, allowing these rules to be offloaded.
114 representor TC rules.
132 access that the IP stack "sees" would then be configurable through tc rules;
172 It is expected that userland will use this information (e.g. through udev rules)
180 How do representors interact with TC rules?
194 ``REP_DEV`` is a VF representor, the following rules::
210 Of course the rules can (if supported by the NIC) include packet-modifying
217 function uplink netdev or port representor). TC rules such as::
[all …]
|
| 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:
|
| /Linux-v6.1/drivers/net/ethernet/mellanox/mlx5/core/lib/ |
| D | fs_ttc.c | 33 struct mlx5_ttc_rule rules[MLX5_NUM_TT]; member
47 if (!IS_ERR_OR_NULL(ttc->rules[i].rule)) { in mlx5_cleanup_ttc_rules()
48 mlx5_del_flow_rules(ttc->rules[i].rule); in mlx5_cleanup_ttc_rules()
49 ttc->rules[i].rule = NULL; in mlx5_cleanup_ttc_rules()
240 struct mlx5_ttc_rule *rules; in mlx5_generate_ttc_table_rules() local
246 rules = ttc->rules; in mlx5_generate_ttc_table_rules()
248 struct mlx5_ttc_rule *rule = &rules[tt]; in mlx5_generate_ttc_table_rules()
400 struct mlx5_ttc_rule *rules; in mlx5_generate_inner_ttc_table_rules() local
406 rules = ttc->rules; in mlx5_generate_inner_ttc_table_rules()
409 struct mlx5_ttc_rule *rule = &rules[tt]; in mlx5_generate_inner_ttc_table_rules()
[all …]
|
| /Linux-v6.1/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()
201 /* Duplicate the given audit watch. The new watch's rules list is initialized
244 /* Update inode info in audit rules based on filesystem event. */
261 /* If the update involves invalidating rules, do the inode-based in audit_update_watch()
277 list_for_each_entry_safe(r, nextr, &owatch->rules, rlist) { in audit_update_watch()
298 list_add(&nentry->rule.rlist, &nwatch->rules); in audit_update_watch()
321 /* Remove all watches & rules associated with a parent that is going away. */
330 list_for_each_entry_safe(r, nextr, &w->rules, rlist) { in audit_remove_parent_watches()
[all …]
|
| /Linux-v6.1/tools/testing/selftests/landlock/ |
| D | fs_test.c | 531 const struct rule rules[]) in create_ruleset() argument
538 ASSERT_NE(NULL, rules) in create_ruleset()
542 ASSERT_NE(NULL, rules[0].path) in create_ruleset()
554 for (i = 0; rules[i].path; i++) { in create_ruleset()
555 add_path_beneath(_metadata, ruleset_fd, rules[i].access, in create_ruleset()
556 rules[i].path); in create_ruleset()
573 const struct rule rules[] = { in TEST_F_FORK() local
583 _metadata, rules[0].access | LANDLOCK_ACCESS_FS_READ_DIR, in TEST_F_FORK()
584 rules); in TEST_F_FORK()
622 const struct rule rules[] = { in TEST_F_FORK() local
[all …]
|
| /Linux-v6.1/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.
102 …check_err_fail $should_fail $? "Attempt to offload $count rules (actual result $((offload_count - …
113 check_err 1 "Invalid count of $count. At most 65536 rules supported"
|
| /Linux-v6.1/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-v6.1/drivers/media/i2c/ccs/ |
| D | ccs-data.h | 91 * @num_if_rules: Number of if rules
92 * @if_rules: If rules
189 * @num_sensor_rules: Number of rules for the sensor
190 * @sensor_rules: Rules for the sensor
196 * @num_module_rules: Number of rules for the module
197 * @module_rules: Rules for the module
|
| /Linux-v6.1/security/integrity/ima/ |
| D | Kconfig | 59 Disabling this option will disregard LSM based policy rules.
132 IMA policy can now be updated multiple times. The new rules get
133 appended to the original policy. Have in mind that the rules are
146 This option allows the root user to see the current policy rules.
173 bool "IMA build time configured policy rules"
180 policy rules persist after loading a custom policy.
182 Depending on the rules configured, this policy may require kernel
|
| D | ima_policy.c | 7 * - initialize default measure policy rules
232 /* An array of architecture specific rules */
387 * lsm rules can change in ima_lsm_copy_rule()
452 * The LSM policy can be reloaded, leaving the IMA LSM based rules referring
453 * to the old, stale LSM policy. Update the IMA LSM based rules to reflect
646 * we need to differentiate between calling hooks, for hook specific rules.
772 * SETXATTR_CHECK rules do not implement a full policy check in ima_update_policy_flags()
850 const char * const *rules; in ima_init_arch_policy() local
858 /* Get number of rules */ in ima_init_arch_policy()
859 for (rules = arch_rules; *rules != NULL; rules++) in ima_init_arch_policy()
[all …]
|
| /Linux-v6.1/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-v6.1/Documentation/userspace-api/ |
| D | landlock.rst | 28 Landlock rules
33 rights`_. A set of rules is aggregated in a ruleset, which can then restrict
39 We first need to define the ruleset that will contain our rules. For this
40 example, the ruleset will contain rules that only allow read actions, but write
84 This enables to create an inclusive ruleset that will contain our rules.
128 It may also be required to create rules following the same logic as explained
197 One policy layer grants access to a file path if at least one of its rules
212 hierarchy is then composed of the exact same files, on which Landlock rules can
213 be tied, either via the source or the destination path. These rules restrict
236 Landlock rules to itself, but they will not be automatically applied to other
[all …]
|
| /Linux-v6.1/drivers/net/ethernet/mellanox/mlx5/core/ |
| D | Kconfig | 52 flow rules to direct traffic into arbitrary rx queue via ethtool set/get_rxnfc
83 offloading rules for traffic between such ports. Supports VLANs (trunk and
106 Say Y here if you want to support offloading connection tracking rules
117 Say Y here if you want to support offloading sample rules via tc
119 If set to N, will not be able to configure tc rules with sample
|
| /Linux-v6.1/security/landlock/ |
| D | ptrace.c | 82 * If the current task has Landlock rules, then the child must have at least
83 * the same rules. Else denied.
100 * If the parent has Landlock rules, then the current task must have the same
101 * or more rules. Else denied.
|
