I have a few more info.
I am trying to run the tests which trigger the issue on two machines, one with 3.2.0-57 and the other with 3.2.0-58.
So far, after 20 runs on each machine, the crash did not happen, so I can't yet confirm the regression.
However, back in october we had another kernel issue, which we solved by not executing anymore the process which was causing it (arping). This was originally tracked under bug 1224001.
I've looked at a crash dump I saved from the time [1], and it's exactly the same.
So I think that the update from 3.2.0-57 to 58 rather than introduce a bug exacerbated a pre-existent condition.
Indeed I also verified that the diff did not introduce any change in the do_exit code path.
Finally, just for the sake of it, I tried to apply [2], but just ended up crashing the kernel at every exit call
Stefan, let me know if there is anything I can do to help you nail down the issue once the bug manifests; I'm not trying to write a script which just obsessively reproduces the sequence of operations which leads to the crash in the hope to have something easily reproducible.
Hi Stefan,
I have a few more info.
I am trying to run the tests which trigger the issue on two machines, one with 3.2.0-57 and the other with 3.2.0-58.
So far, after 20 runs on each machine, the crash did not happen, so I can't yet confirm the regression.
However, back in october we had another kernel issue, which we solved by not executing anymore the process which was causing it (arping). This was originally tracked under bug 1224001.
I've looked at a crash dump I saved from the time [1], and it's exactly the same.
So I think that the update from 3.2.0-57 to 58 rather than introduce a bug exacerbated a pre-existent condition.
Indeed I also verified that the diff did not introduce any change in the do_exit code path.
Finally, just for the sake of it, I tried to apply [2], but just ended up crashing the kernel at every exit call
Stefan, let me know if there is anything I can do to help you nail down the issue once the bug manifests; I'm not trying to write a script which just obsessively reproduces the sequence of operations which leads to the crash in the hope to have something easily reproducible.
[1] http:// paste.openstack .org/show/ 48056/ /kernel. googlesource. com/pub/ scm/linux/ kernel/ git/khilman/ linux-omap- pm/+/8aac62706a daaf0fab02c4327 761561c8bda9448 %5E%21/ #F0
[2] https:/