summaryrefslogtreecommitdiff
path: root/drivers/net/wireguard/Makefile
diff options
context:
space:
mode:
authorJason A. Donenfeld <Jason@zx2c4.com>2023-08-07 15:21:27 +0200
committerJakub Kicinski <kuba@kernel.org>2023-08-07 12:26:57 -0700
commitafb9fa9f88e4387b3c8390b7f54e2b0bdf20828f (patch)
tree736b4a755dcdafe18aaad6f637f9f94e59f201ec /drivers/net/wireguard/Makefile
parent12f632d2d62345a7a7ea58c5106eb68ba2cb9d12 (diff)
downloadwireguard-linux-trimmed-afb9fa9f88e4387b3c8390b7f54e2b0bdf20828f.tar.gz
wireguard-linux-trimmed-afb9fa9f88e4387b3c8390b7f54e2b0bdf20828f.zip
wireguard: allowedips: expand maximum node depth
In the allowedips self-test, nodes are inserted into the tree, but it generated an even amount of nodes, but for checking maximum node depth, there is of course the root node, which makes the total number necessarily odd. With two few nodes added, it never triggered the maximum depth check like it should have. So, add 129 nodes instead of 128 nodes, and do so with a more straightforward scheme, starting with all the bits set, and shifting over one each time. Then increase the maximum depth to 129, and choose a better name for that variable to make it clear that it represents depth as opposed to bits. Cc: stable@vger.kernel.org Fixes: a8f1bc7bdea3 ("net: WireGuard secure network tunnel") Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com> Link: https://lore.kernel.org/r/20230807132146.2191597-2-Jason@zx2c4.com Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'drivers/net/wireguard/Makefile')
0 files changed, 0 insertions, 0 deletions