Comment 40 for bug 843892

Chaskiel,

Your logs show the pings going through in every other run. That's to be expected. My script has poor error handling, and relies on various sleep statements to set things up in order - it's meant to reliably trigger the bug, rather than reliably transmit data. Feel free to fix it up :-)

When you say "When I run the perl script on 2.6.38-12.51, the system does not crash, but the script doesn't behave the same as with 2.6.38-11.51", I would expect you to get oops on 2.6.38-11.51, as that's without my script. So I'm not sure what the word "but" means here, as opposed to "and".

I think your last sentence starting "In addition" you are saying that even with 2.6.8-12.51 you can still trigger a container related oops but with a different non-conntrack related traceback (so probably a different oops), and triggered by a different test case. That should probably be handled separately.

However, when I was looking for this bug, I noticed there were other places (including one in the same file) where nfnetlink_has_listeners() was being called without checking net->nfnl for NULL; in many, net->nfnl can't be NULL no doubt. If it's an oops at the same place (I don't think you attached the oops) you might try fixing it py putting in the obvious check.