diff options
| author | Hao Ge <gehao@kylinos.cn> | 2025-10-23 22:33:13 +0800 |
|---|---|---|
| committer | Vlastimil Babka <vbabka@suse.cz> | 2025-10-24 12:40:13 +0200 |
| commit | 7f434e1d9a17ca5f567c9796c9c105a65c18db9a (patch) | |
| tree | 9bab44fab7b21e3c40bd645da9ca162c0fb08cc0 /tools/docs/parse-headers.py | |
| parent | eecd7cb64178efb35f89aa5134cf6ce36c0c66db (diff) | |
slab: Fix obj_ext mistakenly considered NULL due to race condition
If two competing threads enter alloc_slab_obj_exts(), and the one that
allocates the vector wins the cmpxchg(), the other thread that failed
allocation mistakenly assumes that slab->obj_exts is still empty due to
its own allocation failure. This will then trigger warnings with
CONFIG_MEM_ALLOC_PROFILING_DEBUG checks in the subsequent free path.
Therefore, let's check the result of cmpxchg() to see if marking the
allocation as failed was successful. If it wasn't, check whether the
winning side has succeeded its allocation (it might have been also
marking it as failed) and if yes, return success.
Suggested-by: Harry Yoo <harry.yoo@oracle.com>
Fixes: f7381b911640 ("slab: mark slab->obj_exts allocation failures unconditionally")
Cc: <stable@vger.kernel.org>
Signed-off-by: Hao Ge <gehao@kylinos.cn>
Link: https://patch.msgid.link/20251023143313.1327968-1-hao.ge@linux.dev
Reviewed-by: Suren Baghdasaryan <surenb@google.com>
Reviewed-by: Harry Yoo <harry.yoo@oracle.com>
Signed-off-by: Vlastimil Babka <vbabka@suse.cz>
Diffstat (limited to 'tools/docs/parse-headers.py')
0 files changed, 0 insertions, 0 deletions