Lucid "close race in /proc/*/environ, CVE-2011-1020" causes a lockup regression in chromium-browser. I used a simple google.com search experssion "apparmor dfa" which would reliably lockup the chromium browser. Using strace I was able to determine that it always wedged in a read() call directly after an mmap(). Bisecting lead to commit 7713155dea1f1d29257a044d1e0fe7598e7681dc in git://kernel.ubuntu.com/ubuntu/ubuntu-lucid.git. See attached bisect log. Reverting this single commit appears to have alleviated the lockup.
Lucid "close race in /proc/*/environ, CVE-2011-1020" causes a lockup regression in chromium-browser. I used a simple google.com search experssion "apparmor dfa" which would reliably lockup the chromium browser. Using strace I was able to determine that it always wedged in a read() call directly after an mmap(). Bisecting lead to commit 7713155dea1f1d2 9257a044d1e0fe7 598e7681dc in git://kernel. ubuntu. com/ubuntu/ ubuntu- lucid.git. See attached bisect log. Reverting this single commit appears to have alleviated the lockup.