diff options
| author | Xiubo Li <xiubli@redhat.com> | 2023-04-19 05:39:14 +0300 |
|---|---|---|
| committer | Ilya Dryomov <idryomov@gmail.com> | 2023-04-30 13:37:28 +0300 |
| commit | aaf67de78807c59c35bafb5003d4fb457c764800 (patch) | |
| tree | ca4240b921c125f5ec462f01284da73f6b182ca4 /tools/perf/scripts/python/syscall-counts.py | |
| parent | 7d41870d65db028234333c68e60a034ac335557a (diff) | |
| download | linux-aaf67de78807c59c35bafb5003d4fb457c764800.tar.xz | |
ceph: fix potential use-after-free bug when trimming caps
When trimming the caps and just after the 'session->s_cap_lock' is
released in ceph_iterate_session_caps() the cap maybe removed by
another thread, and when using the stale cap memory in the callbacks
it will trigger use-after-free crash.
We need to check the existence of the cap just after the 'ci->i_ceph_lock'
being acquired. And do nothing if it's already removed.
Cc: stable@vger.kernel.org
Link: https://tracker.ceph.com/issues/43272
Signed-off-by: Xiubo Li <xiubli@redhat.com>
Reviewed-by: Luís Henriques <lhenriques@suse.de>
Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
Diffstat (limited to 'tools/perf/scripts/python/syscall-counts.py')
0 files changed, 0 insertions, 0 deletions