-
-
Notifications
You must be signed in to change notification settings - Fork 30.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Possible kernel crash on vfork #123900
Comments
Hmm, I was under the impression that RPIs ran on MicroPython, not CPython. Could you double check that? If you are running CPython, does this occur on 3.12? 3.11 only gets security fixes now. It would also be helpful if you posted the (Python) code that causes the problem, because I don't see any interpreter functions in the stack trace, so it isn't all that useful. |
Can you write a reproducer? (short code reproducing the crash)
It looks like a kernel bug or a memory corruption. You might try to run your program in Valgrind. |
Indeed, the dereference happens in the kernel, so it's a kernel bug.
The problem is not in CPython, and not even in user space, so Valgrind is irrelevant here. #91401 is also irrelevant (and is itself bogus). If the user believes that vfork() triggers this kernel bug, they might try to reproduce with In any case, this bug should be reported to the maintainers of the kernel used in that Raspberry Pi device, not here. |
Crash report
What happened?
We are running a Python application on a Raspberry Pi Zero 2 W. From time to time, we are getting a kernel crash pointing at
sys_vfork
from thepython
process.While we cannot figure out when that exactely happens and why, I found this issue regarding the use of
vfork
vsfork
and was wondering if this could be the issue #91401.Kernel trace:
CPython versions tested on:
3.11
Operating systems tested on:
Linux
Output from running 'python -VV' on the command line:
Python 3.11.2 (main, May 2 2024, 11:59:00) [GCC 12.2.0]
The text was updated successfully, but these errors were encountered: