| /Linux-v5.4/drivers/net/netdevsim/ |
| D | fib.c | 32 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 …]
|
| /Linux-v5.4/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 | examples.rst | 1 Example of udev rules
7 Example of udev install rules script
|
| /Linux-v5.4/net/netfilter/ |
| D | nf_tables_core.c | 120 struct nft_rule *const *rules; member
153 struct nft_rule *const *rules; in nft_do_chain() local
167 rules = rcu_dereference(chain->rules_gen_1); in nft_do_chain()
169 rules = rcu_dereference(chain->rules_gen_0); in nft_do_chain()
172 rule = *rules; in nft_do_chain()
174 for (; *rules ; rules++) { in nft_do_chain()
175 rule = *rules; in nft_do_chain()
214 jumpstack[stackptr].rules = rules + 1; in nft_do_chain()
235 rules = jumpstack[stackptr].rules; in nft_do_chain()
|
| /Linux-v5.4/tools/perf/util/ |
| 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()
|
| D | strfilter.h | 30 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.4/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-v5.4/Documentation/devicetree/bindings/arm/ |
| D | axentia.txt | 10 and following the rules from atmel-at91.txt for a sama5d31 SoC.
19 and following the rules from above for the axentia,linea CPU module.
28 and following the rules from above for the axentia,linea CPU module.
|
| /Linux-v5.4/Documentation/media/dvb-drivers/ |
| D | udev.rst | 3 UDEV rules for DVB
23 Nevertheless it's now possible to add proper udev rules so that the
48 like you know them. All real distributions out there scan the /etc/udev/rules.d
50 will tell you the directory where the rules are, most likely it's /etc/udev/rules.d/
|
| /Linux-v5.4/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()
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()
331 list_for_each_entry_safe(r, nextr, &w->rules, rlist) { in audit_remove_parent_watches()
396 list_add(&krule->rlist, &watch->rules); in audit_add_to_parent()
455 if (list_empty(&watch->rules)) { in audit_remove_watch_rule()
|
| /Linux-v5.4/net/ceph/crush/ |
| D | crush.c | 123 if (map->rules) { in crush_destroy()
126 crush_destroy_rule(map->rules[b]); in crush_destroy()
127 kfree(map->rules); in crush_destroy()
|
| /Linux-v5.4/security/safesetid/ |
| D | securityfs.c | 68 hash_for_each_safe(pol->rules, bucket, tmp, rule, next) in __release_ruleset()
81 hash_add(pol->rules, &rule->next, __kuid_val(rule->src_uid)); in insert_rule()
90 hash_for_each(pol->rules, bucket, rule, next) { in verify_ruleset()
121 hash_init(pol->rules); in handle_policy_update()
|
| /Linux-v5.4/Documentation/translations/zh_CN/process/ |
| D | index.rst | 33 license-rules
44 stable-kernel-rules
|
| /Linux-v5.4/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-v5.4/Documentation/sound/designs/ |
| D | tracepoints.rst | 116 :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.
|
| /Linux-v5.4/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-v5.4/drivers/net/ethernet/mellanox/mlx5/core/ |
| D | en_fs.c | 675 if (!IS_ERR_OR_NULL(ttc->rules[i])) { in mlx5e_cleanup_ttc_rules()
676 mlx5_del_flow_rules(ttc->rules[i]); in mlx5e_cleanup_ttc_rules()
677 ttc->rules[i] = NULL; in mlx5e_cleanup_ttc_rules()
860 struct mlx5_flow_handle **rules; in mlx5e_generate_ttc_table_rules() local
866 rules = ttc->rules; in mlx5e_generate_ttc_table_rules()
874 rules[tt] = mlx5e_generate_ttc_rule(priv, ft, &dest, in mlx5e_generate_ttc_table_rules()
877 if (IS_ERR(rules[tt])) in mlx5e_generate_ttc_table_rules()
884 rules = ttc->tunnel_rules; in mlx5e_generate_ttc_table_rules()
891 rules[tt] = mlx5e_generate_ttc_rule(priv, ft, &dest, in mlx5e_generate_ttc_table_rules()
894 if (IS_ERR(rules[tt])) in mlx5e_generate_ttc_table_rules()
[all …]
|
| /Linux-v5.4/security/apparmor/include/ |
| D | file.h | 204 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.4/drivers/net/ethernet/mellanox/mlx5/core/en/ |
| D | fs.h | 110 struct mlx5_flow_handle *rules[MLX5E_NUM_TT]; member
138 struct list_head rules; member
179 struct list_head rules; member
|
| /Linux-v5.4/Documentation/networking/ |
| D | tc-actions-env-rules.txt | 2 The "environmental" rules for authors of any new tc actions are:
17 The "environmental" rules for callers of actions (qdiscs etc) are:
|
| D | vrf.txt | 3 The VRF device combined with ip rules provides the ability to create virtual
14 the use of higher priority ip rules (Policy Based Routing, PBR) to take
15 precedence over the VRF device rules directing specific traffic as desired.
41 flow through the VRF device. Similarly on egress routing rules are used to
44 and out of the VRF as a whole.[1] Similarly, netfilter[2] and tc rules can be
45 applied using the VRF device to specify rules that apply to the VRF domain
53 ingress device and both INPUT and PREROUTING rules with skb->dev set to
54 the VRF device. For egress POSTROUTING and OUTPUT rules can be written
67 with a different priority or install per-VRF rules.
69 Prior to the v4.8 kernel iif and oif rules are needed for each VRF device:
[all …]
|
| /Linux-v5.4/Documentation/powerpc/ |
| D | syscall64-abi.rst | 10 rules, with the following differences.
31 Register preservation rules
33 Register preservation rules match the ELF ABI calling sequence with the
93 Register preservation rules
|
| /Linux-v5.4/Documentation/process/ |
| D | index.rst | 22 license-rules
44 stable-kernel-rules
|
| /Linux-v5.4/Documentation/translations/ja_JP/ |
| D | stable_kernel_rules.txt | 2 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.4/samples/bpf/ |
| D | cookie_uid_helper_example.c | 170 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()
|
