diff options
author | Florian Westphal <fw@strlen.de> | 2023-04-11 16:29:47 +0200 |
---|---|---|
committer | Pablo Neira Ayuso <pablo@netfilter.org> | 2023-04-22 01:39:40 +0200 |
commit | 63e9bbbcca60333490e13744ae736d8f988e4950 (patch) | |
tree | ee6c0666b6c814f62b3482336e0cf2452017ce8e /net/mac802154 | |
parent | d4d89e6546e0d1ac09cb9dd353f0cb31c8a8deb1 (diff) | |
download | linux-stable-63e9bbbcca60333490e13744ae736d8f988e4950.tar.gz linux-stable-63e9bbbcca60333490e13744ae736d8f988e4950.tar.bz2 linux-stable-63e9bbbcca60333490e13744ae736d8f988e4950.zip |
netfilter: nf_tables: don't store chain address on jump
Now that the rule trailer/end marker and the rcu head reside in the
same structure, we no longer need to save/restore the chain pointer
when performing/returning from a jump.
We can simply let the trace infra walk the evaluated rule until it
hits the end marker and then fetch the chain pointer from there.
When the rule is NULL (policy tracing), then chain and basechain
pointers were already identical, so just use the basechain.
This cuts size of jumpstack in half, from 256 to 128 bytes in 64bit,
scripts/stackusage says:
nf_tables_core.c:251 nft_do_chain 328 static
Signed-off-by: Florian Westphal <fw@strlen.de>
Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
Diffstat (limited to 'net/mac802154')
0 files changed, 0 insertions, 0 deletions