Home
last modified time | relevance | path

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

12345678910>>...74

/kernel/linux/linux-5.10/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 */
/kernel/linux/linux-4.19/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.c159 struct strfilter *strfilter__new(const char *rules, const char **err) in strfilter__new() argument
165 filter->root = strfilter_node__new(rules, &ep); in strfilter__new()
178 const char *rules, const char **err) in strfilter__append() argument
183 if (!filter || !rules) in strfilter__append()
186 right = strfilter_node__new(rules, &ep); in strfilter__append()
206 int strfilter__or(struct strfilter *filter, const char *rules, const char **err) in strfilter__or() argument
208 return strfilter__append(filter, true, rules, err); in strfilter__or()
211 int strfilter__and(struct strfilter *filter, const char *rules, in strfilter__and() argument
214 return strfilter__append(filter, false, rules, err); in strfilter__and()
237 /* Return true if STR matches the filter rules */
/kernel/linux/linux-5.10/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"
/kernel/linux/linux-4.19/Documentation/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"
/kernel/linux/linux-5.10/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 …]
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()
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,
237 * of rules (composing netmasks) the entries expand to. We compute the worst
254 unsigned long rules; in pipapo_estimate_size() local
260 * field can expand to up to n * 2 rules in each bucket, and in pipapo_estimate_size()
263 rules = ilog2(desc->field_len[i] * BITS_PER_BYTE) * 2; in pipapo_estimate_size()
264 entry_size += rules * in pipapo_estimate_size()
[all …]
/kernel/linux/linux-4.19/net/netfilter/
Dnf_tables_core.c122 struct nft_rule *const *rules; member
144 struct nft_rule *const *rules; in nft_do_chain() local
158 rules = rcu_dereference(chain->rules_gen_1); in nft_do_chain()
160 rules = rcu_dereference(chain->rules_gen_0); in nft_do_chain()
163 rule = *rules; in nft_do_chain()
165 for (; *rules ; rules++) { in nft_do_chain()
166 rule = *rules; in nft_do_chain()
205 jumpstack[stackptr].rules = rules + 1; in nft_do_chain()
227 rules = jumpstack[stackptr].rules; in nft_do_chain()
/kernel/linux/linux-4.19/drivers/net/netdevsim/
Dfib.c32 struct nsim_fib_entry rules; member
52 entry = &fib_data->ipv4.rules; in nsim_fib_get_val()
58 entry = &fib_data->ipv6.rules; in nsim_fib_get_val()
79 entry = &fib_data->ipv4.rules; in nsim_fib_set_max()
85 entry = &fib_data->ipv6.rules; in nsim_fib_set_max()
131 err = nsim_fib_rule_account(&data->ipv4.rules, add, extack); in nsim_fib_rule_event()
134 err = nsim_fib_rule_account(&data->ipv6.rules, add, extack); in nsim_fib_rule_event()
210 data->ipv4.rules.num = 0ULL; in nsim_fib_dump_inconsistent()
213 data->ipv6.rules.num = 0ULL; in nsim_fib_dump_inconsistent()
228 data->ipv4.rules.max = (u64)-1; in nsim_fib_netns_init()
[all …]
/kernel/linux/linux-4.19/security/smack/
DKconfig16 bool "Reporting on access granted by Smack rules"
20 Enable the bring-up ("b") access mode in Smack rules.
25 rules. The developer can use the information to
26 identify which rules are necessary and what accesses
53 delivering a signal in the Smack rules.
/kernel/linux/linux-5.10/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.
/kernel/linux/linux-4.19/Documentation/filesystems/
Ddirectory-locking11 1) read access. Locking rules: caller locks directory we are accessing.
14 2) object creation. Locking rules: same as above, but the lock is taken
17 3) object removal. Locking rules: caller locks parent, finds victim,
20 4) rename() that is _not_ cross-directory. Locking rules: caller locks
29 5) link creation. Locking rules:
37 rules:
52 The rules above obviously guarantee that all directories that are going to be
110 But locking rules for cross-directory rename guarantee that we do not
/kernel/linux/linux-5.10/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
/kernel/linux/linux-5.10/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.
/kernel/linux/linux-4.19/Documentation/sound/designs/
Dtracepoints.rst116 :c:type:`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.
/kernel/linux/linux-5.10/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"
/kernel/linux/linux-5.10/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 …]
/kernel/linux/linux-4.19/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 …]
/kernel/linux/linux-4.19/Documentation/media/dvb-drivers/
Dudev.rst1 UDEV rules for DVB
21 Nevertheless it's now possible to add proper udev rules so that the
46 like you know them. All real distributions out there scan the /etc/udev/rules.d
48 will tell you the directory where the rules are, most likely it's /etc/udev/rules.d/
/kernel/linux/linux-5.10/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 …]
/kernel/linux/linux-5.10/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()

12345678910>>...74