diff options
| author | Leon Romanovsky <leonro@nvidia.com> | 2025-02-19 16:50:58 +0300 |
|---|---|---|
| committer | Steffen Klassert <steffen.klassert@secunet.com> | 2025-02-21 10:08:15 +0300 |
| commit | b6ccf61aa4fda43f7961f2e83433bc6e6b78ab95 (patch) | |
| tree | 110c29342155915d69053bb5b335cd4746065d23 /tools/perf/scripts/python/stackcollapse.py | |
| parent | 585b64f5a62089ef42889b106b063d089feb6599 (diff) | |
| download | linux-b6ccf61aa4fda43f7961f2e83433bc6e6b78ab95.tar.xz | |
xfrm: simplify SA initialization routine
SA replay mode is initialized differently for user-space and
kernel-space users, but the call to xfrm_init_replay() existed in
common path with boolean protection. That caused to situation where
we have two different function orders.
So let's rewrite the SA initialization flow to have same order for
both in-kernel and user-space callers.
Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions