Skip to content

gh-104614: Make Sure ob_type is Always Set Correctly by PyType_Ready() - #105122

Merged
ericsnowcurrently merged 6 commits into
python:mainfrom
ericsnowcurrently:fix-ob-type-before-ready
Jun 1, 2023
Merged

gh-104614: Make Sure ob_type is Always Set Correctly by PyType_Ready()#105122
ericsnowcurrently merged 6 commits into
python:mainfrom
ericsnowcurrently:fix-ob-type-before-ready

Conversation

@ericsnowcurrently

@ericsnowcurrentlyericsnowcurrently commented May 30, 2023

Copy link
Copy Markdown
Member

When I added the relevant condition to type_ready_set_bases() in gh-103912, I had missed that the function also sets tp_base and ob_type (if necessary). That led to problems for third-party static types.

We fix that here, by making those extra operations distinct and by adjusting the condition to be more specific.

@ericsnowcurrently
ericsnowcurrentlyforce-pushed the fix-ob-type-before-ready branch from 116959a to 86f8ec6CompareMay 31, 2023 00:19
@ericsnowcurrently
ericsnowcurrently marked this pull request as ready for review May 31, 2023 00:20
@ericsnowcurrently
ericsnowcurrently removed the request for review from markshannonMay 31, 2023 00:20

@lysnikolaoulysnikolaou left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @ericsnowcurrently! I can verify that this solves numpy/numpy#23766.

@erlend-aasland

Copy link
Copy Markdown
Contributor

Is it possible to use a reduced variant of the numpy case as a regression test?

@lysnikolaou

lysnikolaou commented May 31, 2023

Copy link
Copy Markdown
Member

Without knowing too much around the issue, I was able to come up with this, which is really close to what numpy does (not sure how we would go about adding a test for it).

#definePY_SSIZE_T_CLEAN#include"Python.h"staticPyTypeObjectCustomBaseType1= {
PyVarObject_HEAD_INIT(NULL, 0)
.tp_name="custom.Base1",
.tp_basicsize=sizeof(PyObject),
};
staticPyTypeObjectCustomBaseType2= {
PyVarObject_HEAD_INIT(NULL, 0)
.tp_name="custom.Base2",
.tp_basicsize=sizeof(PyObject),
};
staticPyTypeObjectCustomDerivedType= {
PyVarObject_HEAD_INIT(NULL, 0)
.tp_name="custom.Derived",
.tp_basicsize=sizeof(PyObject),
};
staticPyModuleDefcustommodule= {
PyModuleDef_HEAD_INIT,
.m_name="custom",
.m_doc="Example module that creates an extension type.",
.m_size=-1,
};
PyMODINIT_FUNCPyInit_custom(void)
{
PyObject*m;
if (PyType_Ready(&CustomBaseType1) <0)
returnNULL;
if (PyType_Ready(&CustomBaseType2) <0)
returnNULL;
CustomDerivedType.tp_base=&CustomBaseType2;
CustomDerivedType.tp_bases=Py_BuildValue("(OO)", &CustomBaseType2, &CustomBaseType1);
CustomDerivedType.tp_hash=CustomBaseType1.tp_hash;
if (PyType_Ready(&CustomDerivedType) <0)
returnNULL;
m=PyModule_Create(&custommodule);
if (m==NULL)
returnNULL;
Py_INCREF(&CustomDerivedType);
if (PyModule_AddObject(m, "Custom", (PyObject*) &CustomDerivedType) <0) {
Py_DECREF(&CustomDerivedType);
Py_DECREF(m);
returnNULL;
}
returnm;
}

It segfaults on import on main, and is okay with this PR.

@markshannon

Copy link
Copy Markdown
Member

Would it make sense to allocate the tuples with malloc at start up, and never free them?

There would be no need to free them at the end of the interpreters lifetime, and there would be no issue if an interpreter other than the main interpreter outlives the main interpreter.

@ericsnowcurrently

Copy link
Copy Markdown
MemberAuthor

Would it make sense to allocate the tuples with malloc at start up, and never free them?

Yeah. However, that's orthogonal to this PR.

@ericsnowcurrently

Copy link
Copy Markdown
MemberAuthor

@lysnikolaou, your example helped. I've added a regression test.

@lysnikolaou

Copy link
Copy Markdown
Member

test_capi seems to be failing the first time, but it succeeds when re-run. Not sure what's wrong.

@ericsnowcurrently
ericsnowcurrentlyforce-pushed the fix-ob-type-before-ready branch from 99648fe to 80d20c6CompareJune 1, 2023 21:57
@ericsnowcurrently
ericsnowcurrently enabled auto-merge (squash) June 1, 2023 22:25
@ericsnowcurrently
ericsnowcurrently merged commit 1469393 into python:mainJun 1, 2023
@ericsnowcurrently
ericsnowcurrently deleted the fix-ob-type-before-ready branch June 1, 2023 22:34
@ericsnowcurrentlyericsnowcurrently added the needs backport to 3.12 only security fixes label Jun 1, 2023
@miss-islington

Copy link
Copy Markdown
Contributor

Thanks @ericsnowcurrently for the PR 🌮🎉.. I'm working now to backport this PR to: 3.12.
🐍🍒⛏🤖

miss-islington pushed a commit to miss-islington/cpython that referenced this pull request Jun 1, 2023
…Ready() (pythongh-105122)
When I added the relevant condition to type_ready_set_bases() in pythongh-103912, I had missed that the function also sets tp_base and ob_type (if necessary). That led to problems for third-party static types.
We fix that here, by making those extra operations distinct and by adjusting the condition to be more specific.
(cherry picked from commit 1469393)
Co-authored-by: Eric Snow <ericsnowcurrently@gmail.com>
@bedevere-bot

Copy link
Copy Markdown

GH-105211 is a backport of this pull request to the 3.12 branch.

@bedevere-botbedevere-bot removed the needs backport to 3.12 only security fixes label Jun 1, 2023
ericsnowcurrently pushed a commit that referenced this pull request Jun 1, 2023
…_Ready() (gh-105122) (gh-105211)
When I added the relevant condition to type_ready_set_bases() in gh-103912, I had missed that the function also sets tp_base and ob_type (if necessary). That led to problems for third-party static types.
We fix that here, by making those extra operations distinct and by adjusting the condition to be more specific.
(cherry picked from commit 1469393)
Co-authored-by: Eric Snow ericsnowcurrently@gmail.com
cls->tp_base = (PyTypeObject *)Py_NewRef(base);
cls->tp_bases = Py_BuildValue("(O)", base);
if (cls->tp_bases == NULL) {
return NULL;

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should decref tp_base and tp_bases before returning.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Opened gh-105225.

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for following up after-the-fact!

Comment on lines +1634 to +1640
@classmethod
def setUpClass(cls):
# The tests here don't play nice with our approach to refleak
# detection, so we bail out in that case.
if cls._has_run:
raise unittest.SkipTest('these tests do not support re-running')
cls._has_run = True

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is nice. IMO, we should use a similar approach in test_import instead of the hack suggested in gh-104796.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps also gh-105085 should have been solved like this.

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm glad you appreciate the solution 😄, but actually am a bit torn about this. On the one hand, it gets us what we want in a simple, clear way (IMHO). On the other hand, this approach means there may be code paths that don't get checked for ref leaks, which we'd want to avoid.

If we use this pattern elsewhere, we'll need to be vigilant about making sure we don't miss any ref leak coverage. I'm not sure how easy that would be generally, though it's unlikely that there are more than a handful of tests where we'd want to skip refleak detection. FWIW, in this case I don't think ref leaks are much of a concern.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we should use a similar approach

Wouldn't this skip the whole class Test instead of a smaller def test_...?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, so you make sure to collect all your "ref leak unsafe" tests in a single unittest class.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Alternatively, create a decorator for it.

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants

@ericsnowcurrently@erlend-aasland@lysnikolaou@markshannon@miss-islington@bedevere-bot@sunmy2019