Home
last modified time | relevance | path

Searched full:rules (Results 1 – 25 of 1140) sorted by relevance

12345678910>>...46

/Linux-v5.15/tools/perf/util/
Dstrfilter.h23 * @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 …]
Dstrfilter.c160 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-v5.15/Documentation/admin-guide/aoe/
Dudev.txt1 # 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
Dudev-install.sh1 # 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-v5.15/net/netfilter/
Dnft_set_pipapo.c56 * 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 …]
Dnft_set_pipapo.h52 /* 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 …]
Dnf_tables_core.c129 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-v5.15/kernel/kcsan/
Dpermissive.h3 * 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-v5.15/tools/testing/selftests/landlock/
Dfs_test.c464 const __u64 handled_access_fs, const struct rule rules[]) in create_ruleset() argument
471 ASSERT_NE(NULL, rules) { in create_ruleset()
474 ASSERT_NE(NULL, rules[0].path) { in create_ruleset()
484 for (i = 0; rules[i].path; i++) { in create_ruleset()
485 add_path_beneath(_metadata, ruleset_fd, rules[i].access, in create_ruleset()
486 rules[i].path); in create_ruleset()
502 const struct rule rules[] = { in TEST_F_FORK() local
511 const int ruleset_fd = create_ruleset(_metadata, rules[0].access | in TEST_F_FORK()
512 LANDLOCK_ACCESS_FS_READ_DIR, rules); in TEST_F_FORK()
549 const struct rule rules[] = { in TEST_F_FORK() local
[all …]
/Linux-v5.15/security/smack/
DKconfig17 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-v5.15/Documentation/sound/designs/
Dtracepoints.rst116 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-v5.15/Documentation/filesystems/
Ddirectory-locking.rst16 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-v5.15/Documentation/admin-guide/LSM/
DSmack.rst50 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-v5.15/tools/testing/selftests/drivers/net/mlxsw/
Dtc_flower_scale.sh4 # 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.
101 …check_err_fail $should_fail $? "Attempt to offload $count rules (actual result $((offload_count - …
112 check_err 1 "Invalid count of $count. At most 65536 rules supported"
/Linux-v5.15/drivers/net/ethernet/mellanox/mlx5/core/lib/
Dfs_ttc.c33 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()
396 struct mlx5_ttc_rule *rules; in mlx5_generate_inner_ttc_table_rules() local
402 rules = ttc->rules; in mlx5_generate_inner_ttc_table_rules()
405 struct mlx5_ttc_rule *rule = &rules[tt]; in mlx5_generate_inner_ttc_table_rules()
[all …]
/Linux-v5.15/kernel/
Daudit_watch.c43 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-v5.15/net/sched/
Dem_canid.c34 * 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-v5.15/Documentation/userspace-api/
Dlandlock.rst21 Landlock rules
26 rights`_. A set of rules is aggregated in a ruleset, which can then restrict
32 We first need to create the ruleset that will contain our rules. For this
33 example, the ruleset will contain rules that only allow read actions, but write
137 One policy layer grants access to a file path if at least one of its rules
152 hierarchy is then composed of the exact same files, on which Landlock rules can
153 be tied, either via the source or the destination path. These rules restrict
176 Landlock rules to itself, but they will not be automatically applied to other
192 process, a sandboxed process should have a subset of the target process rules,
235 handle composition of rules. Such property also implies rules nesting.
/Linux-v5.15/tools/testing/selftests/
DMakefile101 # Clear LDFLAGS and MAKEFLAGS when implicit rules are missing. This provides
102 # implicit rules to sub-test Makefiles which avoids build failures in test
103 # Makefile that don't have explicit build rules.
140 # Invoke headers install with --no-builtin-rules to avoid circular
142 # make inherits builtin-rules which will use the rule generate
148 # invokes them as sub-makes and --no-builtin-rules is not necessary,
155 $(MAKE) --no-builtin-rules ARCH=$(ARCH) -C $(top_srcdir) headers_install
157 $(MAKE) --no-builtin-rules INSTALL_HDR_PATH=$$BUILD/usr \
Dlib.mk17 # The following are built by lib.mk common compile rules.
36 # Invoke headers install with --no-builtin-rules to avoid circular
38 # make inherits builtin-rules which will use the rule generate
43 # invokes them as sub-makes and --no-builtin-rules is not necessary,
55 $(MAKE) --no-builtin-rules ARCH=$(ARCH) -C $(top_srcdir) headers_install
57 $(MAKE) --no-builtin-rules INSTALL_HDR_PATH=$$OUTPUT/usr \
/Linux-v5.15/drivers/media/i2c/ccs/
Dccs-data.h91 * @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-v5.15/drivers/gpu/drm/etnaviv/
Dstate_blt.xml.h6 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-v5.15/security/integrity/ima/
DKconfig59 Disabling this option will disregard LSM based policy rules.
134 IMA policy can now be updated multiple times. The new rules get
135 appended to the original policy. Have in mind that the rules are
148 This option allows the root user to see the current policy rules.
175 bool "IMA build time configured policy rules"
182 policy rules persist after loading a custom policy.
184 Depending on the rules configured, this policy may require kernel
/Linux-v5.15/drivers/net/ethernet/netronome/nfp/flower/
Dconntrack.c475 static int nfp_fl_merge_actions_offload(struct flow_rule **rules, in nfp_fl_merge_actions_offload() argument
485 num_actions = rules[CT_TYPE_PRE_CT]->action.num_entries + in nfp_fl_merge_actions_offload()
486 rules[CT_TYPE_NFT]->action.num_entries + in nfp_fl_merge_actions_offload()
487 rules[CT_TYPE_POST_CT]->action.num_entries; in nfp_fl_merge_actions_offload()
494 a_rule->match = rules[CT_TYPE_PRE_CT]->match; in nfp_fl_merge_actions_offload()
498 if (flow_rule_match_key(rules[j], FLOW_DISSECTOR_KEY_BASIC)) { in nfp_fl_merge_actions_offload()
508 flow_rule_match_basic(rules[j], &match); in nfp_fl_merge_actions_offload()
510 a_rule->match = rules[j]->match; in nfp_fl_merge_actions_offload()
513 for (i = 0; i < rules[j]->action.num_entries; i++) { in nfp_fl_merge_actions_offload()
514 a_in = &rules[j]->action.entries[i]; in nfp_fl_merge_actions_offload()
[all …]
/Linux-v5.15/Documentation/networking/
Dtc-actions-env-rules.rst4 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:

12345678910>>...46