[NET] fib_rules: Add no-operation action
The use of nop rules simplifies the usage of goto rules and adds more flexibility as they allow targets to remain while the actual content of the branches can change easly. Signed-off-by: Thomas Graf <tgraf@suug.ch> Signed-off-by: David S. Miller <davem@davemloft.net>
This commit is contained in:
parent
2b44368307
commit
fa0b2d1d21
2 changed files with 4 additions and 2 deletions
|
@ -54,7 +54,7 @@ enum
|
|||
FR_ACT_UNSPEC,
|
||||
FR_ACT_TO_TBL, /* Pass to fixed table */
|
||||
FR_ACT_GOTO, /* Jump to another rule */
|
||||
FR_ACT_RES2,
|
||||
FR_ACT_NOP, /* No operation */
|
||||
FR_ACT_RES3,
|
||||
FR_ACT_RES4,
|
||||
FR_ACT_BLACKHOLE, /* Drop without notification */
|
||||
|
|
|
@ -146,7 +146,9 @@ int fib_rules_lookup(struct fib_rules_ops *ops, struct flowi *fl,
|
|||
rule = target;
|
||||
goto jumped;
|
||||
}
|
||||
} else
|
||||
} else if (rule->action == FR_ACT_NOP)
|
||||
continue;
|
||||
else
|
||||
err = ops->action(rule, fl, flags, arg);
|
||||
|
||||
if (err != -EAGAIN) {
|
||||
|
|
Loading…
Reference in a new issue