aboutsummaryrefslogtreecommitdiffstats
path: root/net/core/utils.c
diff options
context:
space:
mode:
authorDavid S. Miller <[email protected]>2006-09-22 22:17:35 +0000
committerDavid S. Miller <[email protected]>2006-09-22 22:17:35 +0000
commite4bec827feda76d5e7417a2696a75424834d564f (patch)
treebd899e0c2fbf7f6dd1d33ce0610d88fc4a8864ee /net/core/utils.c
parent[XFRM]: Extract common hashing code into xfrm_hash.[ch] (diff)
downloadkernel-e4bec827feda76d5e7417a2696a75424834d564f.tar.gz
kernel-e4bec827feda76d5e7417a2696a75424834d564f.zip
[IPSEC] esp: Defer output IV initialization to first use.
First of all, if the xfrm_state only gets used for input packets this entropy is a complete waste. Secondly, it is often the case that a configuration loads many rules (perhaps even dynamically) and they don't all necessarily ever get used. This get_random_bytes() call was showing up in the profiles for xfrm_state inserts which is how I noticed this. Signed-off-by: David S. Miller <[email protected]>
Diffstat (limited to 'net/core/utils.c')
0 files changed, 0 insertions, 0 deletions