Home
last modified time | relevance | path

Searched refs:rules (Results 1 – 25 of 345) sorted by relevance

12345678910>>...14

/Linux-v5.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
Dexamples.rst1 Example of udev rules
7 Example of udev install rules script
/Linux-v5.10/net/netfilter/
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.c365 int pipapo_refill(unsigned long *map, int len, int rules, unsigned long *dst, in pipapo_refill() argument
378 if (unlikely(i >= rules)) { in pipapo_refill()
460 b = pipapo_refill(res_map, f->bsize, f->rules, fill_map, f->mt, in nft_pipapo_lookup()
563 b = pipapo_refill(res_map, f->bsize, f->rules, fill_map, f->mt, in pipapo_get()
620 static int pipapo_resize(struct nft_pipapo_field *f, int old_rules, int rules) in pipapo_resize() argument
627 new_bucket_size = DIV_ROUND_UP(rules, BITS_PER_LONG); in pipapo_resize()
665 new_mt = kvmalloc(rules * sizeof(*new_mt), GFP_KERNEL); in pipapo_resize()
671 memcpy(new_mt, f->mt, min(old_rules, rules) * sizeof(*new_mt)); in pipapo_resize()
672 if (rules > old_rules) { in pipapo_resize()
674 (rules - old_rules) * sizeof(*new_mt)); in pipapo_resize()
[all …]
Dnft_set_pipapo.h123 unsigned long rules; member
179 int pipapo_refill(unsigned long *map, int len, int rules, unsigned long *dst,
252 unsigned long rules; in pipapo_estimate_size() local
261 rules = ilog2(desc->field_len[i] * BITS_PER_BYTE) * 2; in pipapo_estimate_size()
262 entry_size += rules * in pipapo_estimate_size()
265 entry_size += rules * sizeof(union nft_pipapo_map_bucket); in pipapo_estimate_size()
/Linux-v5.10/tools/perf/util/
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()
Dstrfilter.h30 struct strfilter *strfilter__new(const char *rules, const char **err);
43 const char *rules, const char **err);
56 const char *rules, const char **err);
/Linux-v5.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.
/Linux-v5.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()
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()
329 list_for_each_entry_safe(r, nextr, &w->rules, rlist) { in audit_remove_parent_watches()
394 list_add(&krule->rlist, &watch->rules); in audit_add_to_parent()
453 if (list_empty(&watch->rules)) { in audit_remove_watch_rule()
/Linux-v5.10/net/ceph/crush/
Dcrush.c122 if (map->rules) { in crush_destroy()
125 crush_destroy_rule(map->rules[b]); in crush_destroy()
126 kfree(map->rules); in crush_destroy()
/Linux-v5.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.
/Linux-v5.10/Documentation/ABI/testing/
Dsysfs-block-dm7 Users: util-linux, device-mapper udev rules
16 Users: util-linux, device-mapper udev rules
25 Users: util-linux, device-mapper udev rules
/Linux-v5.10/Documentation/translations/zh_CN/process/
Dindex.rst33 license-rules
46 stable-kernel-rules
/Linux-v5.10/security/safesetid/
Dsecurityfs.c78 hash_for_each_safe(pol->rules, bucket, tmp, rule, next) in __release_ruleset()
91 hash_add(pol->rules, &rule->next, __kuid_val(rule->src_id.uid)); in insert_rule()
93 hash_add(pol->rules, &rule->next, __kgid_val(rule->src_id.gid)); in insert_rule()
104 hash_for_each(pol->rules, bucket, rule, next) { in verify_ruleset()
151 hash_init(pol->rules); in handle_policy_update()
/Linux-v5.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
/Linux-v5.10/security/apparmor/include/
Dfile.h204 static inline void aa_free_file_rules(struct aa_file_rules *rules) in aa_free_file_rules() argument
206 aa_put_dfa(rules->dfa); in aa_free_file_rules()
207 aa_free_domain_entries(&rules->trans); in aa_free_file_rules()
/Linux-v5.10/drivers/net/netdevsim/
Dfib.c38 struct nsim_fib_entry rules; member
99 entry = &fib_data->ipv4.rules; in nsim_fib_get_val()
105 entry = &fib_data->ipv6.rules; in nsim_fib_get_val()
124 entry = &fib_data->ipv4.rules; in nsim_fib_set_max()
130 entry = &fib_data->ipv6.rules; in nsim_fib_set_max()
166 err = nsim_fib_rule_account(&data->ipv4.rules, add, extack); in nsim_fib_rule_event()
169 err = nsim_fib_rule_account(&data->ipv6.rules, add, extack); in nsim_fib_rule_event()
837 data->ipv4.rules.num = 0ULL; in nsim_fib_dump_inconsistent()
838 data->ipv6.rules.num = 0ULL; in nsim_fib_dump_inconsistent()
/Linux-v5.10/Documentation/networking/
Dtc-actions-env-rules.rst8 The "environmental" rules for authors of any new tc actions are:
23 The "environmental" rules for callers of actions (qdiscs etc) are:
Dvrf.rst10 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-v5.10/drivers/net/ethernet/mellanox/mlx5/core/en/
Dfs.h123 struct mlx5e_ttc_rule rules[MLX5E_NUM_TT]; member
174 struct list_head rules; member
215 struct list_head rules; member
/Linux-v5.10/Documentation/process/
Dindex.rst22 license-rules
44 stable-kernel-rules
/Linux-v5.10/Documentation/powerpc/
Dsyscall64-abi.rst19 rules, with the following differences.
47 Register preservation rules
49 Register preservation rules match the ELF ABI calling sequence with the
113 Register preservation rules
/Linux-v5.10/Documentation/translations/ja_JP/
Dstable_kernel_rules.txt2 This is Japanese translated version of "Documentation/process/stable-kernel-rules.rst".
15 linux-2.6.29/Documentation/process/stable-kernel-rules.rst
/Linux-v5.10/samples/bpf/
Dcookie_uid_helper_example.c170 char rules[100]; in prog_attach_iptables() local
178 sprintf(rules, "iptables -A OUTPUT -m bpf --object-pinned %s -j ACCEPT", in prog_attach_iptables()
180 ret = system(rules); in prog_attach_iptables()
/Linux-v5.10/Documentation/arm/
Dkernel_mode_neon.rst55 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:

12345678910>>...14