subtype_dealloc for heap types is a footgun
還沒有人認領這個 Issue。
- 主要語言
- Python
- 星號
- 77.2k
- 分支
- 36k
- PR 合併指標
- PR 指標待擷取
描述
Bug report
Bug description:
#include <Python.h>
static PyType_Slot base_slots[] = {
{0, 0}
};
static PyType_Spec base_spec = {
.name = "Base",
.basicsize = 0,
.itemsize = 0,
.flags = Py_TPFLAGS_DEFAULT | Py_TPFLAGS_BASETYPE,
.slots = base_slots,
};
static void derived_dealloc(PyObject *o) {
// call base class dealloc
destructor base_slot = PyType_GetSlot(Py_TYPE(o), Py_tp_dealloc);
base_slot(o);
}
static PyType_Slot derived_slots[] = {
{Py_tp_dealloc, derived_dealloc},
{0, 0}
};
static PyType_Spec derived_spec = {
.name = "Derived",
.basicsize = 0,
.itemsize = 0,
.flags = Py_TPFLAGS_DEFAULT | Py_TPFLAGS_BASETYPE,
.slots = derived_slots,
};
static int
deallocdemo_module_exec(PyObject *m)
{
PyObject *base_type = PyType_FromModuleAndSpec(
m,
&base_spec,
NULL
);
if (!base_type) return -1;
if (PyModule_AddObjectRef(m, "Base", base_type) < 0) {
Py_DECREF(base_type);
return -1;
}
PyObject *derived_type = PyType_FromModuleAndSpec(
m,
&derived_spec,
base_type
);
Py_DECREF(base_type);
if (!derived_type) return -1;
int add_object_res = PyModule_AddObjectRef(m, "Derived", derived_type);
Py_DECREF(derived_type);
return add_object_res;
}
static PyModuleDef_Slot deallocdemo_module_slots[] = {
{Py_mod_exec, deallocdemo_module_exec},
{0, NULL}
};
static struct PyModuleDef deallocdemo_module = {
.m_base = PyModuleDef_HEAD_INIT,
.m_name = "deallocdemo",
.m_size = 0,
.m_slots = deallocdemo_module_slots,
};
PyMODINIT_FUNC
PyInit_deallocdemo(void)
{
return PyModuleDef_Init(&deallocdemo_module);
}
Essentially, subtype_dealloc prevents any derived type from implementing its own dealloc function. In the example above, trying to destroy a Derived object will cause an infinite loop because subtype_dealloc will call derived_dealloc (which calls subtype_dealloc).
This is something that works better for static-types, where the default was to inherit the tp_dealloc of the base class. I appreciate heap types are a little more complex in the inheritance they allow though.
I suspect this is now too late to change easily, and I can't personally think of any obvious solutions to it. It's obvious possible to work around (by creating a custom tp_dealloc at all levels) so the issue is more "it's a footgun" than "it's unworkable". But it seems worth raising the issue in case it can be improved somehow.
CPython versions tested on:
3.13
Operating systems tested on:
Linux
貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
研究方向
重現程式使用 PyType_FromModuleAndSpec、PyType_GetSlot、Py_tp_dealloc 和 subtype_dealloc;首先追蹤 CPython 型別實作中的這條釋放路徑。使用提供的 Base/Derived 擴充功能作為回歸案例,為堆積型別釋放器建立並測試安全行為;該 issue 未指定測試檔案,也未規定解決方案。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- c, python
- 領域
- backend-api-design
- Issue 類型
- 缺陷
- 難度
- 5/5
- 預估耗時
- 一週以上
- 活躍度
- 停滯
- 描述清晰度
- 需要釐清
- 新手友好度
- 30/100